Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.275 ·

Plain claude runs can now default to a cloud session, with a new --local flag to opt out

Running plain claude can now be automatically routed to a cloud session unless you pass the new --local flag

Group of 6 Use it now No documentation found Internal Changes
JSON All of v2.1.275
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
Internal ChangesKind: in v2.1.275,
What probably matters to youSection of the release

Unclear The finding does not say what consumes defaultedToCloud or how it changes session behavior.

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.

Read from
Names in the bundledefaultedToCloud
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say what consumes `defaultedToCloud` or how it changes session behavior.

See this entry in the whole of v2.1.275 →

Feedback