{"version":"2.1.296","anchor":"prompt-submit-hook-interrupted-while-checking","canonical_anchor":"prompt-submit-hook-interrupted-while-checking","heading":"Interrupting while a prompt-submit hook checks the prompt is now handled","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/prompt-submit-hook-interrupted-while-checking","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Interrupting while a prompt-submit hook checks the prompt is now handled\n\nIf you interrupt while a prompt.submit or UserPromptSubmit hook is checking your prompt, a block still stands and the turn ends as interrupted\n\n**What**\n\nA hook is a script or handler that runs at a set point. `UserPromptSubmit` and `prompt.submit` hooks run when you send a prompt, before Claude works on it, and can block it. Claude Code now handles the case where you interrupt the turn while such a hook is still checking:\n\n- A block the hook already gave still stands. Otherwise there is no verdict.\n\n- The hook result is marked as ended under abort, and earlier messages are kept.\n\n- When the hooks gave no go-ahead, the turn is returned as interrupted, with the message \"the turn was interrupted while the prompt was checked\". Messages are dropped on shutdown.\n\n- A new check looks for any non-built-in `prompt.submit` or `classic.UserPromptSubmit` hooks.\n\n**Why**\n\nAn interrupt at the wrong moment should no longer let a prompt through that a hook had blocked, and one finding says the typed message is no longer lost when you interrupt during these hooks.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}