{"version":"2.1.280","anchor":"cloud-file-sync-failure-message-distinguishes-no-files-at-a","canonical_anchor":"cloud-file-sync-failure-message-distinguishes-no-files-at-a","heading":"Cloud file-sync failure message distinguishes 'no files at all' from 'stale files'","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/cloud-file-sync-failure-message-distinguishes-no-files-at-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Cloud file-sync failure message distinguishes 'no files at all' from 'stale files'\n\nCloud session file-sync error now says whether no files synced at all or the copy is just stale\n\n**What**\n\nWhen Claude Code runs a cloud session (a session running on Anthropic's infrastructure rather than your own machine) and a file repeatedly fails to upload into it, the error message now tells you which of two situations you're in:\n\n- the cloud session has none of your files at all, in which case it offers to start a new cloud session\n\n- the cloud session has an out-of-date or incomplete copy of your files\n\n**Why**\n\nPreviously a sync failure gave you the same message regardless of cause, leaving you to guess whether the fix was to retry or to start over. Knowing which case applies makes it clearer what to do next, and the offer to start a fresh cloud session covers the case where syncing has nothing to build on.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}