{"version":"2.1.317","anchor":"exitplanmode-can-approve-a-claude-doc-as-the-plan","canonical_anchor":"exitplanmode-can-approve-a-claude-doc-as-the-plan","heading":"Plan mode can use a Claude Doc as the plan you approve","tier":"notice","area":"Plan Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/exitplanmode-can-approve-a-claude-doc-as-the-plan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Plan mode can use a Claude Doc as the plan you approve\n\nIn plan mode, Claude can write its plan as a Claude Doc beside the chat, and approving it means Claude carries out the Doc as written\n\n**Unclear.** What switches Doc-based plans on, and whether they are available to anyone yet, is not stated.\n\n**What**\n\nPlan mode is a mode where Claude works out a plan first and waits for your approval before changing anything. Claude ends it with the `ExitPlanMode` tool. Before, the plan was always passed as text or a plan file.\n\nWhen a Claude Doc service is available, a Claude Doc being a document shown beside the chat, Claude is now told to write or revise the plan in a Claude Doc. While planning, the only writes allowed are to that Doc. Then:\n\n- You approve the plan on an approval card that says the plan is the Doc.\n\n- Claude calls `ExitPlanMode` with nothing attached.\n\n- Claude carries out the Doc as it reads at the moment you approve, and is told to read it again before starting work.\n\nThere are also new error messages for cases such as a missing Doc, a Doc plan sent together with extra plan text, and ending up with two Docs. Without a Doc service, plan mode works as before. The tool's own description was unchanged in the prompt capture taken under this release.\n\n**Why**\n\nFor plans kept in a Doc, any edits you make to the Doc before approving are what Claude will carry out.\n\n- Area: Plan Mode\n- Names: `ExitPlanMode`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}