{"version":"2.1.296","anchor":"execfile-output-decoding-and-maxbuffer-handling-reworked","canonical_anchor":"execfile-output-decoding-and-maxbuffer-handling-reworked","heading":"Output from programs Claude Code runs is size-capped and decoded more carefully","tier":"notice","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/execfile-output-decoding-and-maxbuffer-handling-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Output from programs Claude Code runs is size-capped and decoded more carefully\n\nClaude Code now cuts off output from programs it runs when it passes a size limit and marks it as cut off\n\n**What**\n\nWhen Claude Code runs another program and reads what it prints, two things changed:\n\n- Size limit: if the output is bigger than the allowed limit, Claude Code cuts it down and marks it as having gone over the limit.\n\n- Decoding: all output is turned into text the same way, with an option to keep a byte-order mark. That is an invisible marker some files and programs put at the very start of text.\n\n**Why**\n\nVery large output stays within a set size, and text that starts with a byte-order mark can be kept exactly as it was printed.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}