{"version":"2.1.319","anchor":"kept-first-response-now-carries-tool-results-and-skips-alrea","canonical_anchor":"kept-first-response-now-carries-tool-results-and-skips-alrea","heading":"A kept first response no longer re-runs tools that already have results","tier":"notice","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/kept-first-response-now-carries-tool-results-and-skips-alrea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### A kept first response no longer re-runs tools that already have results\n\nWhen Claude Code keeps a first model response, tool requests that already have results are skipped instead of queued again\n\n**What**\n\nSometimes Claude Code keeps the model's first response to reuse it. That response can include tool calls, which are requests from the model for Claude Code to run something such as a command or a file read. Claude Code now also carries over any results those tool calls already have. A tool call that already has a result is skipped and not queued to run again.\n\nBefore, every tool call in a kept response was queued to run, and no earlier results came with it.\n\n**Why**\n\nThis stops tools from running a second time when a response is kept or resumed and the work has already been done.\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}