{"version":"2.1.242","anchor":"archive-sync-explains-conflicts-deletes-and-skipped-files-in","canonical_anchor":"archive-sync-explains-conflicts-deletes-and-skipped-files-in","heading":"Archive sync explains conflicts, deletes and skipped files in plain language","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/archive-sync-explains-conflicts-deletes-and-skipped-files-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Archive sync explains conflicts, deletes and skipped files in plain language\n\nArchive sync now tells you plainly about conflicts, restored deletes and files too large to sync.\n\n**What**\n\nThe archive engine narrates what it did rather than acting silently. Conflicted files are described with where each copy landed, deletes the agent made that you still have locally are reported as restored, oversize files are named as \"too large to sync and will not arrive\", and deferred deletes and uploads are announced as arriving with your next messages. A fresh container is described as having \"came back without this folder's files\".\n\n**Details**\n\n- Each stop condition gets its own line and emits `tengu_dir_sync_stopped`: withdrawn, switched off, lane unavailable, listing abandoned.\n- Pulls and pushes emit `tengu_dir_sync_pull` and `tengu_dir_sync_push` with an outcome and counts of applied, conflicted and trashed files.\n- Setting `CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING` prints a warning that files are read by name and the protection against a cloud session redirecting a read through a swapped directory is off.\n\n**Evidence**\n\n`File sync is reading this folder's files by name (CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING is set): the protection against a cloud session redirecting a read through a swapped directory is off`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}