{"version":"2.1.312","anchor":"plan-slug-tracking-reads-tool-use-result-in-more-shapes-wor","canonical_anchor":"plan-slug-tracking-reads-tool-use-result-in-more-shapes-wor","heading":"Plan tracking reads tool results in more formats","tier":"internal","area":"Plan Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/plan-slug-tracking-reads-tool-use-result-in-more-shapes-wor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Plan tracking reads tool results in more formats\n\nClaude Code now finds a plan's link in more kinds of tool result, and some workshop snapshot tracking was removed\n\n**Unclear.** It is not clear what these changes mean for what you see when using plans.\n\n**What**\n\nWhen Claude Code keeps track of a plan, it reads the result a tool sends back. A tool is one of the actions Claude Code can take. Before, it only understood a result that held a link. It now also understands:\n\n- a result that is an object with a link\n\n- a result that is plain text\n\n- a result that is a list of text pieces, which it reads as structured data\n\nThe tracking of workshop document snapshots was removed, along with the marker for writes to workshop documents. One step that excuses a plan from being checked again now takes different inputs.\n\n**Why**\n\nPlans can now be recognised from more kinds of tool result.\n\n- Area: Plan Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}