Group of 6 Under the hood
Running plain claude can now be automatically routed to a cloud session unless you pass the new --local flag
What
- A new setting (
cloudSessionsByDefault) can cause a plainclaudeinvocation — one with no explicit session, resume, continue, teleport, connect, SSH, worktree, or remote-control flags — to be automatically routed to a cloud session instead of running locally. - A new
--localflag lets you opt out and force a local session; internally the outcome of this decision is tracked as "none", "declined" (for example because--localwas passed), or "applied". - This decision (
defaultedToCloud) is threaded through the session startup configuration, and reported in telemetry, including a newcloud_session_defaultevent fired on cancel, failure, or success.
Why
This means running Claude Code the normal way could start a cloud session rather than a local one, depending on account or organization configuration. The --local flag is how to guarantee you get a local session.
Names in the bundle--remote
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 --remote, on CLI reference.
| `--remote` | Deprecated alias for `--cloud`, including the existing-session form | `claude --remote "Fix the login bug"` |cli-reference see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
what the violin_wood_gate flag itself controls is not stated
Anthropic's documentation agrees
Anthropic's documentation has since written up --remote, on CLI reference.