{"version":"2.1.312","anchor":"plan-workshopmd-sibling-file-support-removed","canonical_anchor":"plan-workshopmd-sibling-file-support-removed","heading":"Plans no longer carry a companion workshop file when forked or resumed","tier":"notice","area":"Plan Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/plan-workshopmd-sibling-file-support-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Plans no longer carry a companion workshop file when forked or resumed\n\nForking or resuming a session copies only the plan's own .md file, not a separate .workshop.md file\n\n**What**\n\nIn plan mode, Claude Code saves the plan to a file named after the plan, ending in `.md`. Before, a second file with the same name ending in `.workshop.md` was handled alongside it. That companion file is no longer handled:\n\n- Forking and resuming: forking a session (starting a new session that branches off an existing one) or resuming one (picking an earlier session back up) copies only the plan's `.md` file.\n\n- Recognising plans: the `.workshop.md` file no longer counts as part of a plan.\n\n- Listing and naming: plan listings, and the check that stops two plans getting the same name, look only at the `.md` file.\n\nThe parts of Claude Code that watch plan files for changes were also reworked.\n\n**Why**\n\nIf you relied on a `.workshop.md` file next to a plan, it will no longer follow the plan into a forked or resumed session.\n\n- Area: Plan Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}