{"version":"2.1.314","anchor":"device-hook-forwarding-input-rewritten-by-matcheraliases","canonical_anchor":"device-hook-forwarding-input-rewritten-by-matcheraliases","heading":"Input sent to device hooks now accounts for the hook's matcher and tool aliases","tier":"notice","area":"Hooks","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/device-hook-forwarding-input-rewritten-by-matcheraliases","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Input sent to device hooks now accounts for the hook's matcher and tool aliases\n\nClaude Code now adjusts the input it forwards to device hooks using the hook's matcher and the tools' alternate names\n\n**What**\n\nHooks are your own commands or scripts that Claude Code runs at set moments, such as before a tool runs. A matcher decides which tools a hook applies to. The input Claude Code forwards to device hooks used to be sent as is. It is now adjusted first, using the hook's matcher and the alternate names that tools go by.\n\n**Why**\n\nRemote hooks may now match tools that appear under a different name.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}