You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
HooksArea: what it touches
Bug FixesKind: in v2.1.296,
Bug FixesSection of the release
What
A 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:
A block the hook already gave still stands. Otherwise there is no verdict.
The hook result is marked as ended under abort, and earlier messages are kept.
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.
A new check looks for any non-built-in prompt.submit or classic.UserPromptSubmit hooks.
Why
An 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.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed Esc or an interrupt during a UserPromptSubmit hook or a mod's prompt.submit hook ending headless sessions, clearing the typed prompt…
