{"version":"2.1.302","anchor":"held-hook-responses-track-whether-they-carry-an-answer-for-t","canonical_anchor":"held-hook-responses-track-whether-they-carry-an-answer-for-t","heading":"Held hook responses now note whether they carry an answer for Claude","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/held-hook-responses-track-whether-they-carry-an-answer-for-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Held hook responses now note whether they carry an answer for Claude\n\nHeld hook output now records whether it holds content meant for Claude, and clearing held hooks also resets one more piece of state\n\n**Unclear.** What the new marker changes in how or when held hook output reaches Claude is not stated.\n\n**What**\n\nA hook is a command you configure to run at certain points while Claude works. Claude Code can hold a hook's response before passing it on. It now marks a held response when that response has content meant for Claude. Clearing all held hooks now also resets a marker saying the session's environment is out of date.\n\n**Why**\n\nThis affects how output from held hooks is delivered.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}