{"version":"2.1.319","anchor":"exitplanmode-reads-the-approved-plan-doc-itself","canonical_anchor":"exitplanmode-reads-the-approved-plan-doc-itself","heading":"Leaving plan mode now loads the approved plan Doc directly","tier":"notice","area":"Plan Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/exitplanmode-reads-the-approved-plan-doc-itself","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Leaving plan mode now loads the approved plan Doc directly\n\nWhen you approve a plan kept in a Claude Doc, Claude Code now reads that Doc itself instead of asking the model to\n\n**Unclear.** What switches on the plan-in-a-Doc mode is not settled.\n\n**What**\n\nWhen a plan is kept in a Claude Doc and you approve it, leaving plan mode (the mode where Claude proposes a plan before making changes) now reads the approved Doc and hands it to the model as the plan, along with any attachments. Before, Claude Code only told the model to go and read the Doc before doing anything else.\n\nThis applies when the Docs connector tool is present and the plan is in Doc mode. If the Doc cannot be read, for example because it is not on record or no reader is available, Claude Code logs the failure.\n\n**Why**\n\nThe approved plan now reaches the model every time, rather than depending on the model following an instruction to fetch it.\n\n- Area: Plan Mode\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}