{"version":"2.1.281","anchor":"cloud-file-sync-skip-warning-now-says-why","canonical_anchor":"cloud-file-sync-skip-warning-now-says-why","heading":"Cloud file-sync skip warning now says why","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-skip-warning-now-says-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud file-sync skip warning now says why\n\nThe warning about cloud file changes not being copied to your machine now includes the reason\n\n**What**\n\nClaude Code sometimes skips copying files from a cloud session (a session running on remote machines) to your computer because of an `anchor_degraded` condition. When it does, the warning now starts with a fixed sentence and ends with the reason:\n\n\"Files Claude changed in the cloud were not placed on this machine and stay in the cloud session: \" followed by the formatted reason from `anchor?.byNameReason`.\n\n**Why**\n\nYou can see why your local files were not updated, and the warning tells you the changes are still in the cloud session rather than lost."}