You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Cloud SessionsArea: what it touches
RemovedKind: in v2.1.232,
RemovedSection of the release
What
--ref and --on-branch now require --cloud or --environment even when --project is given, and the resulting error adds a clause explaining that --project alone is not enough. The remote-project field was dropped from the session options that get built.
Details
--project still applies to Remote Control, where a session's project is fixed at creation: disconnect first, then re-run /remote-control --project to start a new one.
Evidence
--project no longer starts cloud sessions
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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.
Added sinceA small documentation edit on Environment variables touched a line naming --cloud after this was published.| `CCR_FORCE_BUNDLE` | Set to `1` to force [`claude --cloud`](/docs/en/claude-code-on-the-web#send-local-repositories-without-github) to bundle and upload your local repository instead of cloning from its remote |env-varssee the edit
Confirmed sinceAnthropic's documentation has since written up --cloud, on Use Claude Code on the web.`--cloud` works with a single repository at a time. The task runs in the cloud while you continue working locally. The older `--remote` spelling still works as a deprecated alias for `--cloud`.claude-code-on-the-websee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --cloud, on Use Claude Code on the web.
Anthropic's release notes agreeRemote Control: resuming a conversation no longer silently takes Remote Control away from another Claude Code on the same machine that still…
