Cloud startup now explains unusual checkout shapes, including that nothing syncs back and pushes won't work.
What's wrong with this entry?
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.
- Whether you see these depends entirely on the shape of your checkout; there is no flag.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
worktree.locationsetting for Desktop SSH sessionsBoth mention worktree
-
v2.1.246
Worktree cleanup only removes directories Claude Code created
Both mention worktree
-
v2.1.248
Background sessions adopt an existing worktree at startup
Both mention worktree