Cloud commits wait rather than apply when the branch is checked out in another worktree.
What's wrong with this entry?
When directory sync would fast-forward a branch that is also checked out in another worktree, it now waits instead of applying, with a reason of checked_out_elsewhere and a line explaining that applying Claude's cloud commits there would make them look undone in the other tree. If that worktree is gone, git worktree prune clears the block.
- Before applying an incoming cloud commit the checkout's worktrees are enumerated, honouring
core.bare,extensions.worktreeConfigand per-worktree config, plus rebase and bisect head-name files. - The same check runs again at commit time, not only before the apply.
- No flag; this is on for everyone using directory sync.
checked_out_elsewhere, which would then show them as undone there
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.247
Cloud-session seeding names linked worktrees and split git layouts as un-seedable
Both mention worktree
-
v2.1.247
Start-up explanations for unusual checkout shapes
Both mention worktree