{"version":"2.1.299","anchor":"prompt-submit-hook-chain-rewritten-to-handle-slash-commands","canonical_anchor":"prompt-submit-hook-chain-rewritten-to-handle-slash-commands","heading":"Prompts rewritten by a hook can now be refused with a \"no place to put the change\" message","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/prompt-submit-hook-chain-rewritten-to-handle-slash-commands","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Prompts rewritten by a hook can now be refused with a \"no place to put the change\" message\n\nPrompt hooks now see slash command names and arguments, and some rewrites stop the prompt with a \"Prompt not sent\" message\n\n**Unclear.** It is not clear which kinds of hook changes lead to the \"Prompt not sent\" message.\n\n**What**\n\nWhen you submit a prompt, `UserPromptSubmit` hooks can look at it and change it. A hook is a command of your own that Claude Code runs at set moments. The prompt now carries the slash command's name and arguments through to those hooks.\n\nThere is also a new message: \"Prompt not sent: ... changed it, and Claude Code has no place to put the change.\" It appears when a change cannot be applied to the prompt.\n\n**Why**\n\n`UserPromptSubmit` hooks that rewrite slash commands may behave differently than before.\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"}