{"version":"2.1.281","anchor":"dir-sync-user-facing-warning-when-the-cloud-checkout-had-re","canonical_anchor":"dir-sync-user-facing-warning-when-the-cloud-checkout-had-re","heading":"Dir-sync: user-facing warning when the cloud checkout had rewound your branch","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dir-sync-user-facing-warning-when-the-cloud-checkout-had-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Dir-sync: user-facing warning when the cloud checkout had rewound your branch\n\nDirectory sync now warns you when Claude's cloud checkout had gone back past commits on your branch\n\n**What**\n\nWhen Claude Code syncs a cloud session with the folder on your machine, you can now see a new notice. It says Claude's copy in the cloud had gone back past a number of commits on your branch, that the branch has now been restored, and that Claude was told. It also says some files may show up as uncommitted changes, and it mentions `git restore <file>` for dealing with them.\n\nThis notice replaces an older helper that only checked whether a file was empty or not.\n\n**Why**\n\nYou find out when the cloud copy had rolled your branch back, and you know to check for files that arrive as uncommitted changes afterwards.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}