{"version":"2.1.280","anchor":"new-file-sync-error-messages-for-corruption-rewritten-histo","canonical_anchor":"new-file-sync-error-messages-for-corruption-rewritten-histo","heading":"New file-sync error messages for corruption, rewritten history, and a full file store","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-file-sync-error-messages-for-corruption-rewritten-histo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New file-sync error messages for corruption, rewritten history, and a full file store\n\nNew error messages explain file-sync failures from data corruption, rewritten history, or a full file store\n\n**What**\n\nClaude Code adds new user-facing error messages for file sync in cloud sessions, covering: a git object that \"fails its checksum\" (data corruption), history that was rewritten partway through a session, and a cloud session's file store being full. There's also a separate recovery message shown once the full-store condition clears.\n\n**Why**\n\nThese give clearer, more specific explanations when file sync runs into trouble, instead of a generic failure message, and let a reader know when a full file store has been resolved and syncing can continue.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}