{"version":"2.1.277","anchor":"git-dir-sync-checkout-gains-new-terminal-states","canonical_anchor":"git-dir-sync-checkout-gains-new-terminal-states","heading":"Git dir-sync checkout gains new terminal states","tier":"internal","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/git-dir-sync-checkout-gains-new-terminal-states","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Git dir-sync checkout gains new terminal states\n\nDirectory sync's git checkout logic gains several new named outcome states\n\n**What**\n\nThe directory-sync feature, which checks out git state to keep a synced copy up to date, now recognizes several new outcome states for a checkout operation:\n\n- `checkout_mid_operation`\n\n- `checkout_unmerged`\n\n- `checkout_unborn`\n\n- `checkout_unreadable`\n\n- `snapshot_refused`\n\n- `no_ref`\n\n- `acknowledge`\n\n- `other`\n\nA new sync kind, `checkout_empty`, was also added.\n\n**Why**\n\nMore granular outcome tracking lets Claude Code distinguish between different reasons a directory-sync checkout didn't complete cleanly, such as a repository mid-operation, unmerged paths, or an unborn branch, rather than lumping them together.\n\n- Area: Directory Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}