{"version":"2.1.283","anchor":"cloud-dir-sync-gains-an-anchor-unavailable-fallback-with-i","canonical_anchor":"cloud-dir-sync-gains-an-anchor-unavailable-fallback-with-i","heading":"Cloud folder sync stops with an explanation when files cannot be placed safely","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/cloud-dir-sync-gains-an-anchor-unavailable-fallback-with-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud folder sync stops with an explanation when files cannot be placed safely\n\nIf this machine cannot safely place synced files, folder sync for cloud sessions stops and Claude works directly on this machine instead\n\n**Unclear.** What makes files unsafe to place, and what controls whether directory sync runs at all, is not stated.\n\n**What**\n\nDirectory sync copies a local folder or git checkout so a cloud session can work on it. It now has a specific stop reason for when this machine cannot safely place files in the target location.\n\nWhen that happens, Claude Code shows a notice and falls back to working on your local machine directly, with the message \"this machine cannot place files safely here; Claude works on this machine directly\". The event is also recorded in usage data, noting whether a folder or a checkout was involved.\n\n**Why**\n\nSync now stops cleanly and tells you why, where before this kind of failure had no reason of its own.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}