{"version":"2.1.281","anchor":"message-after-directory-sync-stops-now-says-the-cloud-copy-w","canonical_anchor":"message-after-directory-sync-stops-now-says-the-cloud-copy-w","heading":"Message after directory sync stops now says the cloud copy was moved, not deleted","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/message-after-directory-sync-stops-now-says-the-cloud-copy-w","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Message after directory sync stops now says the cloud copy was moved, not deleted\n\nWhen directory sync stops, Claude is now told the synced copy was moved to a set-aside directory, not deleted\n\n**Unclear.** The finding does not give the name of the set-aside directory or say what starts directory sync.\n\n**What**\n\nWhen directory sync stops and the session's synced copy is cleared, Claude Code tells the model what happened to those files. That message now says everything was moved under a named set-aside directory and was not deleted.\n\n**Why**\n\nThe model gets an accurate picture of where the files went. It is less likely to tell you your work is gone, and it can point you to where the files now are."}