{"version":"2.1.265","anchor":"truncated-tool-output-persist-message-now-distinguishes-cap","canonical_anchor":"persisted-tool-results-are-now-size-capped-with-truncation-r","heading":"Persisted tool results are now truncated to a byte cap, with truncation reported","tier":"notice","area":"Tool Results","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/truncated-tool-output-persist-message-now-distinguishes-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Persisted tool results are now truncated to a byte cap, with truncation reported\n\nLarge tool outputs saved to disk are now capped in size, and the CLI reports when truncation happened\n\n**What**\n\n- When Claude saves a large tool result to disk, the content is now capped to a byte budget (1GiB by default) using an encoding-aware truncator.\n\n- The saved result records a new `truncatedAtBytes` field when truncation happened, plus a derived `truncatedAtCap` boolean alongside `estimatedOriginalTokens`\/`estimatedPersistedTokens`.\n\n- The message shown to you after a tool result is saved now distinguishes a full save from a truncated one, telling you only the first N bytes were saved when the cap kicked in.\n\n**Why** Without a cap, an unusually large tool result could produce an oversized file on disk; the new byte cap keeps saved files bounded, and the accompanying message and tracking fields let you (and Claude) know when a saved copy is incomplete rather than assuming it's the full result.\n\n- Area: Tool Results\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}