{"version":"2.1.295","anchor":"hook-output-redirected-blocking-hooks-may-be-answered-elsew","canonical_anchor":"hook-output-redirected-blocking-hooks-may-be-answered-elsew","heading":"Web-address hooks can now be blocked with a message","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/hook-output-redirected-blocking-hooks-may-be-answered-elsew","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Web-address hooks can now be blocked with a message\n\nThe part of Claude Code that runs hooks gained an extra check for web-address hooks that can block an action with a message\n\n**Unclear.** It is not stated what makes the new check block an HTTP hook or what the held-answer marker changes.\n\n**What**\n\nA hook is something you configure to run automatically at a set moment, either a script on your machine or a request to a web address (an HTTP hook). The part of Claude Code that runs hooks now has an extra check for HTTP hooks that can block the action and show a message. Hook results also now carry an extra marker saying whether the answer was held.\n\n**Why**\n\nThis may change when HTTP hooks and script hooks end up blocking an action.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}