{"version":"2.1.275","anchor":"new-cloud-session-default-telemetry-path-and-violin-wood","canonical_anchor":"cloud-sessions-by-default-plain-claude-invocations-can-be","heading":"Plain claude runs can now default to a cloud session, with a new --local flag to opt out","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-cloud-session-default-telemetry-path-and-violin-wood","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Plain `claude` runs can now default to a cloud session, with a new --local flag to opt out\n\nRunning plain `claude` can now be automatically routed to a cloud session unless you pass the new --local flag\n\n**Unclear.** what the violin_wood_gate flag itself controls is not stated\n\n**What**\n\n- A new setting (`cloudSessionsByDefault`) can cause a plain `claude` invocation \u2014 one with no explicit session, resume, continue, teleport, connect, SSH, worktree, or remote-control flags \u2014 to be automatically routed to a cloud session instead of running locally.\n\n- 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\".\n\n- 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.\n\n**Why**\n\nThis 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.\n\n- Area: Sessions\n- Names: `--remote`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}