{"version":"2.1.283","anchor":"file-sync-new-anchor-unavailable-refusal-when-this-machine","canonical_anchor":"file-sync-new-anchor-unavailable-refusal-when-this-machine","heading":"File sync refuses to start when this machine cannot place files safely","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/file-sync-new-anchor-unavailable-refusal-when-this-machine","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### File sync refuses to start when this machine cannot place files safely\n\nFolder sync now stops with a clear refusal when this machine cannot place its files safely, instead of carrying on in a degraded way\n\n**Unclear.** It is not clear which platforms or conditions make the anchor unavailable.\n\n**What**\n\nFile sync copies a folder between this machine and a cloud session. Before a sync starts, Claude Code opens an anchor, the fixed point it uses to place files. Before, a failure here was only logged as \"tree anchor not opened\". Now:\n\n- If the anchor is unavailable, starting a folder sync is refused with the message \"this machine cannot place its files safely\" and details of why.\n\n- If the anchor cannot be read at all, a separate \"unreadable\" message is given.\n\n- A sync already running saves its record and stops.\n\n- Two background checks return no result instead of failing, and one logs that there is no anchored backend here.\n\n- The upload step no longer hides errors from opening the anchor.\n\n**Why**\n\nOn machines where the anchor cannot work, you now get a plain refusal instead of a sync that quietly runs in a reduced state.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}