{"version":"2.1.247","anchor":"huge-hook-output-no-longer-floods-error-messages","canonical_anchor":"huge-hook-output-no-longer-floods-error-messages","heading":"Huge hook output no longer floods error messages","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/huge-hook-output-no-longer-floods-error-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Huge hook output no longer floods error messages\n\nA hook that dumps huge output now gives you a readable error instead of a wall of text.\n\n**What**\n\nOversized hook output and error stacks are now cut down the middle with a marker saying how many characters were removed, so a hook that dumps a large stdout produces a readable failure instead of a wall of text.\n\n**Details**\n\n- The count in the marker accounts for characters already elided by nested markers, so it stays accurate.\n- Errors are formatted as name and message plus at most five stack frames, each clipped to a line length.\n- Applied to worktree-create hook failure output.\n\n**Evidence**\n\n`characters truncated`\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}