What probably matters to youSection of the release
Unclear Whether cloudSessionsByDefault is on for any given account is decided server-side and not stated by this finding.
What
A new setting (cloudSessionsByDefault) can cause a plain claude invocation — 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 --local flag lets you opt out and force a local session; internally the outcome of this decision is tracked as "none", "declined" (for example because --local was passed), or "applied".
This decision (defaultedToCloud) is threaded through the session startup configuration, and reported in telemetry, including a new cloud_session_default event 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether cloudSessionsByDefault is on for any given account is decided server-side and not stated by this finding.
Anthropic's release notes agreeFixed --resume, the resume picker preview, resumed background agents and the transcript view failing on a session whose saved history…
