Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.296 ·

Interrupting while a prompt-submit hook checks the prompt is now handled

If you interrupt while a prompt.submit or UserPromptSubmit hook is checking your prompt, a block still stands and the turn ends as interrupted

Group of 3 You'll notice Bug Fixes
JSON All of v2.1.296
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.

Read from
Names in the bundleprompt.submit
What the documentation says
prompt.submit React to events with a mod modified, high confidence The same handler shape fits a guard on `prompt.submit` or `config.set`. When `next.called` is false, return the refusal that the [events reference](/docs/en/plugins/mods/reference#events) lists for that event: `{ drop: 'the reason' }` for … see the edit
prompt.submit Troubleshoot a mod modified, high confidence The line starts with the mod's name and names a `$.prompt.submit`, `$.command.run`, or `$.agent.spawn` call, as in `first-mod: its session.start ran again in a fresh copy; the $.prompt.submit call it had already made was not made again`. C… see the edit
prompt.submit Claude Code changelog modified, high confidence * Fixed a prompt that a mod's `prompt.submit` hook rewrote or dropped still being saved as typed to prompt history and to the transcript's queued-prompt records see the edit
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up prompt.submit, on Claude Code changelog. * Added `$.prompt.media` so a `prompt.submit` hook of a mod installed by managed settings can read the bytes of an image or document attached to the prompt changelog see the edit
Added since A small documentation edit on Mods reference touched a line naming prompt.submit after this was published. When another mod's hook calls a method on a namespace you added in `engine.create`, your method's `$` calls run in that hook's context until every hook on that event returns. For example, a relative path resolves against that hook's workin… plugins/mods/reference see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesprompt.submit on React to events with a mod
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…

See this entry in the whole of v2.1.296 →

Feedback