{"version":"2.1.248","anchor":"cloud-directory-sync-says-when-the-checkout-cannot-be-snapsh","canonical_anchor":"cloud-directory-sync-says-when-the-checkout-cannot-be-snapsh","heading":"Cloud directory sync says when the checkout cannot be snapshotted","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cloud-directory-sync-says-when-the-checkout-cannot-be-snapsh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cloud directory sync says when the checkout cannot be snapshotted\n\nClaude is told when a mid-merge or conflicted checkout meant your file changes never got sent.\n\n**What**\n\nWhen a cloud session's checkout is mid-merge, rebase or cherry-pick, holds unresolved conflicts, has an unborn branch, or cannot be read, Claude is now told this turn's file changes were not sent and instructed not to claim the files arrived.\n\n**Evidence**\n\n`a merge, rebase or cherry-pick is under way in it`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}