{"version":"2.1.283","anchor":"directory-sync-no-longer-falls-back-to-unanchored-by-name-fi","canonical_anchor":"directory-sync-no-longer-falls-back-to-unanchored-by-name-fi","heading":"Directory sync refuses to place files on machines that cannot anchor folders","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/directory-sync-no-longer-falls-back-to-unanchored-by-name-fi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Directory sync refuses to place files on machines that cannot anchor folders\n\nDirectory sync now gives up instead of placing files by name when folder anchoring is unavailable, unless CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING is set\n\n**Unclear.** It is not clear what, if anything, is shown to you when sync gives up because anchoring is unavailable.\n\n**What**\n\nDirectory sync is Claude Code's syncing of a folder with a cloud session. Anchoring is how it keeps a fixed hold on a folder while placing files, rather than going by the folder's name each time. On some machines anchoring cannot be used. Examples are a missing native interface, a missing Linux process filesystem, an unstable folder identity, or a platform that is not supported.\n\nOn those machines, directory sync used to fall back to placing files by name, limited to the root folder. It now reports anchoring as unavailable and gives up instead.\n\nPlacing files by name now happens only when you set `CLAUDE_CODE_DIR_SYNC_DISABLE_ANCHORING`, and in that mode it is no longer limited to the root folder. The related error message now names that variable.\n\n**Why**\n\nPlacing files by name is less safe than anchoring, so refusing is the safer default. The cost is that on machines without anchoring support, files from the cloud may not be downloaded.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}