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.247 Home All releases ←olderv2.1.246 v2.1.248newer→
Claude Code v2.1.247

Cloud-session seeding names linked worktrees and split git layouts as un-seedable

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

Starting a cloud session from a linked worktree now explains why and tells you to use the main checkout.

git worktree add
What

Starting a cloud session from a checkout made with git worktree add, or from one whose git directory lives outside the working tree, now gets its own refusal and remedy instead of a generic failure. The advice is to start from the repository's main checkout or an ordinary clone.

Details
  • Two new verdicts, linked_worktree and unserved_layout, each carry their own explanation text.
  • Both still defer to the repository-too-large message when that was the recorded reason.
  • The seed payloads for the remote_ref and overlay cases no longer carry a tree hash or the timestamp it was read at.
Evidence

this checkout is a linked working tree (git worktree add), whose commits and changes this machine cannot yet compare with GitHub

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