{"version":"2.1.242","anchor":"files-claude-deletes-in-a-cloud-session-go-to-a-session-tras","canonical_anchor":"files-claude-deletes-in-a-cloud-session-go-to-a-session-tras","heading":"Files Claude deletes in a cloud session go to a session trash, with a reason for every case","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/files-claude-deletes-in-a-cloud-session-go-to-a-session-tras","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Files Claude deletes in a cloud session go to a session trash, with a reason for every case\n\nDeletions from a cloud session move your files to a session trash, never erasing them.\n\n**What**\n\nDirectory sync can now bring deletions back down to your machine, and it never erases anything: removed files are moved to a per-session trash folder. Each refusal has its own user-facing line, so you can see why a delete was skipped.\n\n**Details**\n\n- Deletes are refused in bursts, capped per turn, and skipped entirely when no trash folder can be created.\n- Skipped for protected names, credential-looking names, symlinked names, and when `.git` sits on a different volume.\n- Kept, not deleted, when your local copy changed or does not match what Claude removed. Conflicted copies sit beside the files they belong to.\n- Bookkeeping (state, staging, trash) lives in a `.ccr-dir-sync` directory at the top of the working tree, which the model is told to ignore.\n- Each sync engine has its own enabled check driven by remote config; the archive engine's check raises \"directory sync flag unknown just now\" when the flag has not resolved yet, so what happens before it resolves depends on the server.\n\n**Evidence**\n\n`conflicted copies sit beside the files they belong to.`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}