Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

--project no longer starts a cloud session

You'll notice
Useful3 Signal3
Cloud Sessions not in their notes

Passing --project alone won't start a cloud session; --ref and --on-branch now need --cloud or --environment.

--project--ref--on-branch--cloud--environment
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →