{"version":"2.1.299","anchor":"userpromptsubmit-hook-blocked-prompt-reasons-and-commandis","canonical_anchor":"userpromptsubmit-hook-blocked-prompt-reasons-and-commandis","heading":"UserPromptSubmit hooks get more detail about the prompt","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/userpromptsubmit-hook-blocked-prompt-reasons-and-commandis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### UserPromptSubmit hooks get more detail about the prompt\n\nInformation prepared for `UserPromptSubmit` hooks now includes the command and whether the prompt is an internal one\n\n**Unclear.** It is not confirmed that `command` and `isMeta` reach the input your hook script receives.\n\n**What**\n\nA `UserPromptSubmit` hook is a command you set to run when a prompt is submitted, before Claude works on it. Claude Code has changed how it handles these:\n\n- The information prepared for the hook now includes `command` and `isMeta`, taken from the submitted prompt.\n\n- When a prompt is blocked because the hooks never ran, the block now carries a reason saying so.\n\n- Warnings now say whether the prompt was kept.\n\n**Why**\n\nHooks can tell apart prompts that come from a slash command or from Claude Code itself, rather than from what you typed.\n\n- Area: Hooks\n- Names: `UserPromptSubmit`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}