{"version":"2.1.321","anchor":"truncated-tool-output-notice-now-explains-shared-limits-acro","canonical_anchor":"truncated-tool-output-notice-now-explains-shared-limits-acro","heading":"Notes on cut-short tool output now mention other large results in the same reply","tier":"notice","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/truncated-tool-output-notice-now-explains-shared-limits-acro","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Notes on cut-short tool output now mention other large results in the same reply\n\nWhen oversized tool output is cut short, Claude is now told if other large results in the same reply caused part of the shortening\n\n**What**\n\nA tool call is one action Claude takes, such as running a command or reading a file. When a tool returns too much output and it cannot be saved, Claude sees a note saying only the first part is shown and the rest was dropped. If other tool calls in the same reply also returned oversized results, the note now adds a sentence saying this part is shorter because of that. The note no longer always ends with the same fixed hint to page through or filter the output.\n\n**Why**\n\nIn practice, Claude gets a more accurate explanation of why output is missing when it runs several tools at once.\n\n- Area: Tools\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}