{"version":"2.1.290","anchor":"pretooluse-hook-presence-check-takes-an-extra-tool-name-argu","canonical_anchor":"pretooluse-hook-presence-check-takes-an-extra-tool-name-argu","heading":"PreToolUse hooks can be matched against more than one tool name","tier":"notice","area":"Hooks","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/pretooluse-hook-presence-check-takes-an-extra-tool-name-argu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### PreToolUse hooks can be matched against more than one tool name\n\nClaude Code's check for PreToolUse hooks now matches against a wider list of names worked out from an extra tool name, not just one\n\n**Unclear.** It is not clear what the extra names are or what `bypassCapabilityNotification` does.\n\n**What**\n\nA `PreToolUse` hook is a command you set up to run just before a tool call executes. A tool call is one action Claude takes, such as editing a file or running a shell command, and the hook can block it. When Claude Code checks whether any `PreToolUse` hook applies to a tool call, it can now be given a second tool name. It adds extra names worked out from that one to the list it matches your hooks against. Before, it matched against a single tool name.\n\nThe permission information Claude Code passes around for a tool call can also carry a new optional field called `bypassCapabilityNotification`.\n\n**Why**\n\nIn practice, a `PreToolUse` hook may now run for a tool call that reaches it under a different name than the one the hook was written for.\n\n- Area: Hooks\n- Names: `PreToolUse`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}