Forwarding permissions.defaultMode and effort into claude --remote and reporting the decision both sit behind remote flags with no compiled value.
Claude Code can now take the default permission mode and effort level from your local settings, forward them into a session started with claude --remote, and report at startup what it decided. Both halves sit behind remote feature flags that have no value compiled into this build, so with no server configuration a remote session still starts without your local permissions.defaultMode and nothing about the decision is reported.
- Forwarding requires the remote flag
tengu_violin_strad, which is looked up from the server, has no value compiled into the build, and is treated as false if the lookup throws. - The forwarding check ANDs an existing precondition with that flag lookup, and its single result is passed to remote-session setup both as the general gate and as the flag deciding whether the settings mode is forwardable.
- A new helper assembles the startup report: whether a settings default was considered, whether one is present, its value, the active mode and the effort.
- Every field of that report except the presence bit,
settingsDefaultModePresent, is blanked unless bothtengu_violin_woodandtengu_violin_stradare on, and both are compiled with a false fallback.
tengu_violin_strad, settingsDefaultModePresent
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_violin_strad Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.238: not a boolean we can read
tengu_violin_wood Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.238: off
Read once, for one account on one subscription tier, against v2.1.238. It isn't a statement about your account. What a flag value here can and cannot tell you
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.
* Signed out, from `/remote-control` or `--remote-control`: `Remote Control requires a claude.ai subscription.` or `/remote-control requires a claude.ai subscription.`remote-control see the edit
| Read from the highest-priority source only | Reads the key only from the highest-priority source that carries a policy key, so a lower source's value is ignored even when the highest source sets none | [`apiKeyHelper`](#apikeyhelper), [`…settings-reference see the edit
`--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
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Anthropic's documentation has since written up --remote, on Use Claude Code on the web.
New in this build: tengu_violin_strad