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.238 Home All releases ←olderv2.1.237 v2.1.239newer→
Claude Code v2.1.238

claude --cloud explains when your local changes cannot be uploaded

Use it now
Useful3 Signal2
Cloud Sessions not in their notes

claude --cloud now says why your local changes could not be uploaded and points you at --ref.

--cloud--ref
What

Starting a cloud session that cannot ship your working tree now says no session was started and why: either the local changes were too large, or bundling them failed. Both messages point you at --ref <branch> to start from GitHub instead, with file sync off.

Details
  • The two reasons are distinguished internally as local_changes_too_large and local_changes_bundle_failed.
Evidence

so the working tree cannot be uploaded instead

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.238 →