{"version":"2.1.283","anchor":"file-sync-dir-sync-seeding-now-refused-for-zerolimited-da","canonical_anchor":"file-sync-dir-sync-seeding-now-refused-for-zerolimited-da","heading":"Cloud file sync is turned off for organizations with limited data retention","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/file-sync-dir-sync-seeding-now-refused-for-zerolimited-da","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud file sync is turned off for organizations with limited data retention\n\nOrganizations under zero or limited data retention no longer get local-to-cloud file sync in cloud sessions and now see a notice explaining why\n\n**What**\n\nWhen Claude Code starts a cloud session, one that runs on a remote machine, it can copy your local folder or checkout there to start from. It now checks your organization's compliance policy first.\n\nIf your organization has zero data retention or limited data retention:\n\n- your folder or checkout is not copied to the cloud session\n\n- you see the notice \"File sync is not available for your organization: its data retention policy does not allow it.\"\n\n- when sync is refused, Claude is told the reason and that its changes exist only in the cloud session\n\n**Why**\n\nFor these organizations, file sync between your computer and a `--cloud` session is unavailable, and you now get a clear reason instead of a sync that quietly fails.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}