{"version":"2.1.247","anchor":"userpromptsubmit-hooks-now-run-over-the-prompt-text-that-act","canonical_anchor":"userpromptsubmit-hooks-now-run-over-the-prompt-text-that-act","heading":"UserPromptSubmit hooks now run over the prompt text that actually wins","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/userpromptsubmit-hooks-now-run-over-the-prompt-text-that-act","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### UserPromptSubmit hooks now run over the prompt text that actually wins\n\nPrompt-submit hooks now run over the final prompt text, and cancellations report as cancelled not failed.\n\n**What**\n\nHooks 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.\n\n**Details**\n\n- A chain that drops the prompt with no run to attribute it to now produces a message prefixed `Prompt dropped by a hook:`.\n- A new failure covers the case where the hooks never saw the submitted text at all.\n- Applies to everyone; there is no gate on this path.\n\n**Evidence**\n\n`Prompt blocked: the UserPromptSubmit hooks did not run over the submitted text.`\n\n- Area: Hooks\n- Names: `UserPromptSubmit`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}