{"version":"2.1.321","anchor":"oversized-tool-results-that-cant-be-saved-get-a-new-truncat","canonical_anchor":"oversized-tool-results-that-cant-be-saved-get-a-new-truncat","heading":"Clearer message to Claude when a tool's output is too large to save","tier":"notice","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/oversized-tool-results-that-cant-be-saved-get-a-new-truncat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Clearer message to Claude when a tool's output is too large to save\n\nWhen a tool's output is too large and cannot be saved, Claude is now told only the first part was kept and how to fetch the rest\n\n**What**\n\nA tool call is a single action Claude takes, such as running a command or reading a file. When a tool call's output is too large and Claude Code cannot save the full output, Claude receives a message about it. That message has been reworded. It now says:\n\n- the output was too large and could not be saved, so only the first part is shown and the rest was dropped\n\n- when several calls in one reply overflow, those results share one limit\n\n- Claude can page through the output, filter it, or repeat the call with fewer calls per reply\n\n**Why**\n\nClaude gets clearer guidance when part of a tool's output is lost, so it can try a better way to get what it needs instead of working from incomplete results.\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}