{"version":"2.1.283","anchor":"claude-cloud-directory-sync-restore-refuses-a-target-with","canonical_anchor":"claude-cloud-directory-sync-restore-refuses-a-target-with","heading":"Cloud session folder sync handles full storage and unrestorable targets differently","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/claude-cloud-directory-sync-restore-refuses-a-target-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud session folder sync handles full storage and unrestorable targets differently\n\nFolder sync for claude --cloud now keeps a turn in the cloud when its store is full and refuses a restore with no base to start from\n\n**Unclear.** The setting that controls this sync was not traced, so who gets this behaviour is unclear.\n\n**What**\n\nWhen `--cloud` runs a session in the cloud, Claude Code can sync a folder and later restore an earlier state of it. This changed in three ways:\n\n- Restoring a target that has no base to rebuild from now stops with a \"no basis\" result.\n\n- When the store is full, the turn's work stays in the cloud and is marked as not sent back.\n\n- A restore is now either full or partial. The separate \"last turn\" kind is gone.\n\n**Why**\n\nIf a cloud session's store fills up, some work may stay in the cloud rather than reach your folder.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}