{"version":"2.1.282","anchor":"stopping-file-sync-no-longer-empties-the-cloud-sessions-cop","canonical_anchor":"stopping-file-sync-no-longer-empties-the-cloud-sessions-cop","heading":"Stopping file sync now says both copies keep their files","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/stopping-file-sync-no-longer-empties-the-cloud-sessions-cop","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Stopping file sync now says both copies keep their files\n\nThe message shown when file sync stops now says neither the cloud copy nor your local folder loses any files, and they become separate copies\n\n**Unclear.** Only the message was seen to change; whether the cloud copy is actually no longer emptied is not confirmed.\n\n**What**\n\nFile sync keeps a folder on your machine and a cloud session's copy of your project in step. The message Claude Code shows when file sync stops has been rewritten. It now says nothing is removed on either side: the cloud session's checkout and your local folder both keep their files, and from then on they are separate copies. To move work between them you use git, the version control tool.\n\nThe old message said the cloud session would be told to empty its copy before Claude's next turn there.\n\n**Why**\n\nIf the wording matches what Claude Code does, stopping sync no longer throws away the files in the cloud session. Any work you want to carry over between the two copies after that has to go through git.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}