{"version":"2.1.239","anchor":"commands-that-produce-too-much-output-now-say-so","canonical_anchor":"commands-that-produce-too-much-output-now-say-so","heading":"Commands that produce too much output now say so","tier":"notice","area":"Bash Tool","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/commands-that-produce-too-much-output-now-say-so","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Commands that produce too much output now say so\n\nA command that floods its output is now reported as truncated instead of looking like a crash.\n\n**What**\n\nWhen a spawned command exceeds the output buffer limit, the helper that runs it now returns an explicit overflow marker alongside the exit code instead of a generic failure, so the code that called it can tell truncated output apart from a crashed command.\n\n**Evidence**\n\n`execFileNoThrow maxBuffer exceeded`\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}