{"version":"2.1.296","anchor":"background-hook-json-parsing-is-capped","canonical_anchor":"background-hook-json-parsing-is-capped","heading":"Very large or deeply nested background hook output is no longer fully read","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/background-hook-json-parsing-is-capped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Very large or deeply nested background hook output is no longer fully read\n\nClaude Code now limits how many JSON keys and how much nesting it reads from a background hook's output\n\n**Unclear.** It is not clear when this limit applies, since an unidentified check decides whether the old unlimited reading is used instead.\n\n**What**\n\nA background hook is a command of your own that Claude Code runs without waiting on it. Hooks can print JSON, a structured text format, as their answer. Claude Code now limits how many keys it will read from that output in total, and how deeply it may nest. Output past either limit is not read. Claude Code logs an error asking the hook to print one answer with fewer keys. An answer with an empty payload is now treated as empty.\n\n**Why**\n\nVery large hook output could otherwise slow Claude Code down or swamp it. If you write hooks, keep their JSON answers small.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}