What
The messages shown when a cloud session starts gained two reasons covering a checkout made with git worktree add and one whose git directory sits outside the working tree. A linked working tree's changes are carried into the session, but nothing syncs back and the session cannot push to GitHub.
Details
- Whether you see these depends entirely on the shape of your checkout; there is no flag.
Evidence
this checkout keeps its git directory outside the working tree (a .git file, or a git directory elsewhere), a shape 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.