{"version":"2.1.246","anchor":"cloud-commits-are-held-back-when-the-branch-is-checked-out-i","canonical_anchor":"cloud-commits-are-held-back-when-the-branch-is-checked-out-i","heading":"Cloud commits are held back when the branch is checked out in another worktree","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/cloud-commits-are-held-back-when-the-branch-is-checked-out-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Cloud commits are held back when the branch is checked out in another worktree\n\nCloud commits wait rather than apply when the branch is checked out in another worktree.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Before applying an incoming cloud commit the checkout's worktrees are enumerated, honouring `core.bare`, `extensions.worktreeConfig` and per-worktree config, plus rebase and bisect head-name files.\n- The same check runs again at commit time, not only before the apply.\n- No flag; this is on for everyone using directory sync.\n\n**Evidence**\n\n`checked_out_elsewhere`, `which would then show them as undone there`\n\n- Area: Directory Sync\n- Names: `git worktree prune`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}