What
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.
Details
- 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.
Evidence
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.
Names in the bundlegit worktree prune