{"version":"2.1.284","anchor":"elicitation-hooks-that-signal-a-block-now-always-block","canonical_anchor":"elicitation-hooks-that-signal-a-block-now-always-block","heading":"Elicitation hooks that ask to block now always block","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/elicitation-hooks-that-signal-a-block-now-always-block","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Elicitation hooks that ask to block now always block\n\nAn Elicitation hook that signals a block now always blocks, even if it also reports success or its output is empty or not JSON\n\n**What**\n\nA hook is a command you configure that Claude Code runs at a certain point. For hooks on the Elicitation event, a hook result marked as blocked now stops the request straight away with a blocking error. This happens whether or not the hook also reported success.\n\nBefore, a hook marked as both blocked and succeeded was ignored if its output was empty or was not JSON (a structured text format), and the request went ahead.\n\n**Why**\n\nAn Elicitation hook meant to block can no longer be silently skipped because of how its output was formatted.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}