{"version":"2.1.246","anchor":"container-side-file-sync-engine-gone","canonical_anchor":"container-side-file-sync-engine-gone","heading":"Container-side file sync engine gone","tier":"notice","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/container-side-file-sync-engine-gone","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Container-side file sync engine gone\n\nThe old container file-sync engine and all its sync warning messages are gone from your transcripts.\n\n**What**\n\nThe older sync engine that ran inside cloud containers and mirrored a directory to the checkout on your machine has been removed, along with every notice it inserted before your messages: the explanation that the directory is synced, the auth-failing, auth-restored and halted warnings, and the \"files not copied into this session\" notices. You will not see those messages again on this build.\n\n**Details**\n\n- Its per-turn pull and push loop and its trash and conflict bookkeeping under `.ccr-dir-sync` are gone.\n- Its telemetry events for pull, push, base, rehome and the first-turn hold no longer occur anywhere in the build.\n- Only a leftover record-path helper still mentions the directory name.\n\n**Evidence**\n\n`File sync with the user's machine has stopped for the rest of this session`\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}