Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.246entry #69

Claude Code v2.1.246 ·

Forwarding your home settings to a cloud session now records explicit consent

Forwarding your home settings to a cloud session now records your consent separately from permission.

Use it now Improvements
JSON All of v2.1.246
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
ImprovementsKind: in v2.1.246,
What probably matters to youSection of the release
What

--forward-home-settings (used with --cloud or --environment) no longer just flips a boolean. Startup resolves a consent value and passes it through to session creation, so the fact that you consented is tracked separately from whether forwarding is allowed at all, and a settings-upload status feed now sits alongside the existing file-sync one.

Details
  • Consent is carried into the create call and reported in telemetry as home_settings_host_consent; the created session's permission mode is echoed back.
  • A new refusal reason covers sessions "launched from your home directory (or above it, or inside a checkout rooted there)", which cannot be bound.
  • The launch options dropped a settings-plan wait timeout in favour of the consent value, and the consent-surface check can now be short-circuited by the host's answer.
Evidence

home_settings_host_consent, homeSettingsConsent, replaceHomeSettingsHostConsent, launched from your home directory (or above it, or inside a checkout rooted there)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle--forward-home-settings--cloud--environment
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up --environment, on Write a credential helper. Set [`inferenceCredentialHelperArgs`](/docs/third-party/claude-desktop/configuration#inferencecredentialhelperargs) to a JSON array of strings to pass arguments to the helper. Claude Desktop passes each entry to the executable as one argum… third-party/claude-desktop/credential-helper see the edit
Added since A small documentation edit on Environment variables touched a line naming --cloud after this was published. | `CCR_FORCE_BUNDLE` | Set to `1` to force [`claude --cloud`](/docs/en/claude-code-on-the-web#send-local-repositories-without-github) to bundle and upload your local repository instead of cloning from its remote | env-vars see the edit
Confirmed since Anthropic's documentation has since written up --cloud, on Use Claude Code on the web. `--cloud` works with a single repository at a time. The task runs in the cloud while you continue working locally. The older `--remote` spelling still works as a deprecated alias for `--cloud`. claude-code-on-the-web see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --cloud, on Use Claude Code on the web.

See this entry in the whole of v2.1.246 →

Feedback