Prompt-submit hooks now run over the final prompt text, and cancellations report as cancelled not failed.
What's wrong with this entry?
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.
- 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.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.242
Prompts pass through a submit hook chain that can rewrite or drop them
Both mention prompt submit hook
-
v2.1.238
Prompt-expansion hooks can hide the original prompt from a block message
Both mention user prompt hook