{"version":"2.1.312","anchor":"markdown-artifacts-always-use-the-plan-template-workshop-pa","canonical_anchor":"markdown-artifacts-always-use-the-plan-template-workshop-pa","heading":"Markdown artifacts always render with the plan template","tier":"notice","area":"Artifacts","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/markdown-artifacts-always-use-the-plan-template-workshop-pa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Markdown artifacts always render with the plan template\n\nMarkdown artifacts are now always rendered with the bundled plan template, and the separate handling for workshop pages has been removed\n\n**Unclear.** It is not clear whether workshop pages were removed entirely or only moved somewhere else.\n\n**What**\n\nAn artifact is a page Claude Code publishes from a file it wrote. When Claude Code publishes a markdown (`.md`) artifact, it now converts it in one way only, using the plan template that ships with Claude Code. Several pieces of handling for workshop pages are gone:\n\n- Workshop pages no longer get their own markdown converter, which used to be chosen when a feature check was on.\n\n- Workshop documents are no longer saved as file snapshots. Only the plan is snapshotted.\n\n- Live editing no longer refuses with \"live-edit is not available on workshop pages\".\n\nIf the template cannot be loaded, Claude Code reports \"md artifact: template load failed\".\n\n**Why**\n\nThe workshop-page feature appears to have been taken out of this path, so every markdown artifact now looks like a plan page.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}