{"version":"2.1.265","anchor":"oversized-output-error-message-now-warns-about-byte-limited","canonical_anchor":"oversized-output-error-message-now-warns-about-byte-limited","heading":"Oversized-output error message now warns about byte-limited saved files","tier":"notice","area":"Tool Results","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/oversized-output-error-message-now-warns-about-byte-limited","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Oversized-output error message now warns about byte-limited saved files\n\nError messages for oversized tool output now warn when the saved file itself was truncated\n\n**What**\n\nWhen a tool's output is too large to show directly and Claude Code saves it to a file instead, that saved file can itself be cut off at a byte limit. Now, when this happens, the error message shown to Claude explicitly notes that the saved file only contains the first N bytes or characters of the original output, that it may end in the middle of a structure, and that trying to parse it as JSON can therefore fail.\n\n**Why**\n\nThis extra warning helps Claude (and anyone reading the error) understand why a saved file might fail to parse, instead of appearing to be a mysterious JSON error.\n\n- Area: Tool Results\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}