{"version":"2.1.280","anchor":"cloud-session-sync-new-file-store-full-failure-reason","canonical_anchor":"cloud-session-sync-new-file-store-full-failure-reason","heading":"Cloud session sync: new 'file store full' failure reason","tier":"notice","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/cloud-session-sync-new-file-store-full-failure-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Cloud session sync: new 'file store full' failure reason\n\nCloud session sync now reports a specific 'file store full' error when the upload lane fills up\n\n**What**\n\nWhen syncing a cloud or background session's files, Claude Code now recognizes a `lane_full` response from the server (shown internally as `file_store_full`) and displays a clear message telling you the session's cloud file store is full, explaining that Claude will keep working on your machine directly. This joins other existing sync failure reasons like `refused`, `too_large`, and `withdrawn`, and falls back to local-only operation the same way those do.\n\n**Why**\n\nThis gives a clearer, specific explanation when a cloud session can't sync because its upload capacity is full, instead of a generic failure, while still letting work continue locally.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}