{"version":"2.1.282","anchor":"clearer-error-when-a-folder-sessions-starting-snapshot-is-g","canonical_anchor":"clearer-error-when-a-folder-sessions-starting-snapshot-is-g","heading":"Separate message when a folder session's starting snapshot has been removed","tier":"notice","area":"File Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/clearer-error-when-a-folder-sessions-starting-snapshot-is-g","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Separate message when a folder session's starting snapshot has been removed\n\nFolder-sync sessions now say plainly when their starting snapshot is gone, instead of reporting it as a read error\n\n**What**\n\nA folder-sync session keeps snapshots of your folder on this machine, each one building on the one before, starting from a first snapshot. Claude Code now tells apart two problems that used to share one error:\n\n- The starting snapshot is gone: removed, cleaned up, or thrown away as damaged. The message explains that every later snapshot depends on it and that only a new cloud session from this folder starts afresh.\n\n- The starting snapshot could not be read. This keeps its own message.\n\n**Why**\n\nWhen a cloud folder session cannot resume, you get a more specific reason and a clearer idea of what to do next.\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}