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_worktreeandunserved_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_refandoverlaycases 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.
Names in the bundlegit worktree add
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.
Confirmed since
Anthropic's documentation has since written up git worktree add, on Run parallel sessions with worktrees.
All of these apply whether you create the worktree with `--worktree`, with `git worktree add`, or through the [desktop app](/docs/en/desktop#work-in-parallel-with-sessions).worktrees see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up git worktree add, on Run parallel sessions with worktrees.