{"version":"2.1.281","anchor":"dir-sync-many-new-model-notices-when-the-user-and-cloud-his","canonical_anchor":"dir-sync-many-new-model-notices-when-the-user-and-cloud-his","heading":"Dir-sync: many new model notices when the user and cloud histories diverge","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/dir-sync-many-new-model-notices-when-the-user-and-cloud-his","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Dir-sync: many new model notices when the user and cloud histories diverge\n\nAfter directory sync in cloud sessions, Claude now gets notices for more cases where your history and the cloud's differ\n\n**What**\n\nIn cloud sessions, Claude Code keeps the folder on your machine and the copy in the cloud in step, which is called directory sync. After a sync, Claude receives short notices about anything unusual. These notices now cover new cases:\n\n- Rewound commits whose files no longer match are named, and Claude is told to check `git diff HEAD -- PATH`.\n\n- Commits already on a remote are no longer re-created on top of your current commit, and Claude is told not to cherry-pick them (copy them over one by one).\n\n- When a file of yours sits where Claude had a directory, Claude's files are moved to the session trash.\n\n- Files not yet written because they were based on an out-of-date copy are listed with the note \"sync settles this by itself\".\n\n- A new notice covers the case where your machine cut a list short.\n\n**Why**\n\nWhen your history and the cloud copy disagree, Claude is now told what happened and what to do about it. It should avoid duplicating commits that are already on a remote and avoid acting on files that sync will fix by itself.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}