{"version":"2.1.286","anchor":"hook-rewritten-prompt-now-applied-to-the-matched-user-messag","canonical_anchor":"hook-rewritten-prompt-now-applied-to-the-matched-user-messag","heading":"Prompts rewritten by a hook now reach Claude as rewritten","tier":"notice","area":"Hooks","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/hook-rewritten-prompt-now-applied-to-the-matched-user-messag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Prompts rewritten by a hook now reach Claude as rewritten\n\nWhen a hook rewrites your prompt on submit, Claude Code now applies the new text to your message so Claude sees the rewritten version\n\n**Unclear.** It is not certain the old behaviour was actually broken in practice.\n\n**What**\n\nA hook is a script or plugin step that runs at a set point, here when you submit a prompt. When such a hook rewrites your prompt, Claude Code now puts the new text into your actual message, whether it is plain text or made of several parts. Before, the rewrite could land on the wrong object, leaving Claude to see the prompt as you typed it.\n\n**Why**\n\nHooks that change or add to your prompt should now have their changes seen by Claude.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}