{"version":"2.1.296","anchor":"prompt-submit-hook-handling-blocked-prompt-tracking-and-abo","canonical_anchor":"prompt-submit-hook-handling-blocked-prompt-tracking-and-abo","heading":"Prompt-submit hooks that block after an interrupt now end as an interruption","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/prompt-submit-hook-handling-blocked-prompt-tracking-and-abo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Prompt-submit hooks that block after an interrupt now end as an interruption\n\nIf a prompt-submit hook blocks your prompt after the session was interrupted, Claude Code now treats it as an interruption instead of a normal block\n\n**Unclear.** It is not clear what you see differently when a prompt-submit hook blocks after an interrupt.\n\n**What**\n\nA hook is a command you configure to run automatically at a set moment. A `UserPromptSubmit` hook runs each time you send a prompt and can block it. Claude Code now keeps track of hook runs that have not finished yet, and records the text that goes with a blocked prompt.\n\nIf such a hook blocks a prompt after the session has already been interrupted, Claude Code now stops with an interruption instead of returning an ordinary blocked result.\n\n**Why**\n\nThis changes how prompt-submit hooks behave when you interrupt Claude Code while they are still running.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}