{"version":"2.1.299","anchor":"planworkshop-file-helpers-become-no-ops-when-a-session-does","canonical_anchor":"planworkshop-file-helpers-become-no-ops-when-a-session-does","heading":"Plan files are skipped in sessions that do not write to disk","tier":"internal","area":"Diskless Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/planworkshop-file-helpers-become-no-ops-when-a-session-does","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Plan files are skipped in sessions that do not write to disk\n\nSessions that do not write to disk no longer read, write or recover plan files, and saving an ultraplan in one fails with an error\n\n**Unclear.** It is not clear which kinds of session count as not writing to disk.\n\n**What**\n\nIn sessions that do not write to disk, Claude Code now skips its plan-file handling:\n\n- reading and writing plan files\n\n- copying plan files when a session is resumed or forked (split into a new copy)\n\n- recovering workshop documents\n\nSaving an ultraplan in such a session now fails with the message \"Cannot save the plan: this session does not write to disk\". Before, plan files were always read and written.\n\n**Why**\n\nIn sessions without disk storage, plan files are no longer created or recovered, and an ultraplan save fails with a clear message instead of failing silently.\n\n- Area: Diskless Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}