Group of 6 Use it now Notable
No documentation found
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 bundlecloudSessionsByDefault
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Whether cloudSessionsByDefault is on for any given account is decided server-side and not stated by this finding.
Anthropic's release notes agree
Fixed --resume, the resume picker preview, resumed background agents and the transcript view failing on a session whose saved history…