{"version":"2.1.283","anchor":"session-sync-store-full-now-keeps-the-work-locally-instea","canonical_anchor":"session-sync-store-full-now-keeps-the-work-locally-instea","heading":"A full remote store now counts as work kept locally instead of a failure","tier":"internal","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/session-sync-store-full-now-keeps-the-work-locally-instea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### A full remote store now counts as work kept locally instead of a failure\n\nWhen the remote store is full, the result is now reported as kept on this machine rather than as a failure\n\n**Unclear.** It is unclear which sync or transfer feature this result belongs to.\n\n**What**\n\nWhen Claude Code tries to send work to a remote store and the store reports that it is full, the result is now treated the same way as work that is over its size cap. It is reported as kept on this machine and is not recorded as still owed to the store. Before, a full store was reported as a failure.\n\n**Why**\n\nA full remote store now shows up as work held locally rather than as an error.\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}