{"version":"2.1.323","anchor":"oversized-tool-results-keep-carried-markers-persisted-outpu","canonical_anchor":"oversized-tool-results-keep-carried-markers-persisted-outpu","heading":"Shortened tool output now explains a shared size limit","tier":"notice","area":"Tool Results","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/oversized-tool-results-keep-carried-markers-persisted-outpu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Shortened tool output now explains a shared size limit\n\nOversized tool results saved to disk keep their markers, and a new note explains when output is short because several results share one limit\n\n**What**\n\nA tool call is one action Claude takes, such as running a command or reading a file. When its result is too large, Claude Code saves it to disk and shows Claude a shortened preview instead. Two things change:\n\n- Markers found in the original result are now copied into the preview.\n\n- A new note explains when a preview is short because other tool calls in the same reply also produced results too large to save, and those results share one limit.\n\n**Why**\n\nClaude gets a clearer explanation of why some output was cut short, so it is less likely to misread a short result as the whole result.\n\n- Area: Tool Results\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}