You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.247,
What probably matters to youSection of the release
What
Hooks you configure for prompt submission are now run as part of the plugin prompt chain instead of standalone. Results are cached per input text and only committed once the chain settles, so a prompt rewritten upstream gets the hooks run over the final text rather than a discarded draft. Cancellation from the abort signal, or a hook cancelled without timing out, is now reported as a cancellation instead of a failure.
Details
A chain that drops the prompt with no run to attribute it to now produces a message prefixed Prompt dropped by a hook:.
A new failure covers the case where the hooks never saw the submitted text at all.
Applies to everyone; there is no gate on this path.
Evidence
Prompt blocked: the UserPromptSubmit hooks did not run over the submitted text.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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.
Added sinceA small documentation edit on Hooks reference touched a line naming UserPromptSubmit after this was published.In addition to the [common input fields](#common-input-fields), UserPromptSubmit hooks receive the `prompt` field containing the text the user submitted. Pasted content that collapsed to a `[Pasted text #N]` placeholder arrives expanded in…hookssee the edit
Confirmed sinceAnthropic's documentation has since written up UserPromptSubmit, on Hooks reference.* per turn: `UserPromptSubmit`, `Stop`, and `StopFailure`hookssee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up UserPromptSubmit, on Hooks reference.
