{"version":"2.1.281","anchor":"cloud-file-sync-specific-reasons-when-sync-is-not-set-up","canonical_anchor":"cloud-file-sync-specific-reasons-when-sync-is-not-set-up","heading":"Cloud file sync: specific reasons when sync is not set up","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-specific-reasons-when-sync-is-not-set-up","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud file sync: specific reasons when sync is not set up\n\nCloud file sync now gives two specific reasons when it is not set up: GitHub access not confirmed, or cloud starting point unknown\n\n**What**\n\nWhen cloud file sync is not set up, Claude Code shows a reason. There are two new reasons:\n\n- `preflight_failed`: Claude's access to the repository on GitHub could not be confirmed when the session was created. The message tells you to check the GitHub integration at [https:\/\/claude.ai\/code](https:\/\/claude.ai\/code), then start a new session.\n\n- `no_container_origin`: this computer could not work out what the cloud session's copy of the project started from.\n\n**Why**\n\nInstead of a general \"not set up\", you learn the actual cause. For the GitHub case you also get the fix: check the integration, then start a new session.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}