What
Hooks are commands that run automatically when Claude uses a tool. In the /hooks menu, the list of matchers (the rules that choose which tools a hook applies to) is now drawn as list rows. Each row has:
- a dimmed badge showing where the hook comes from
- the matcher, or "(all)" when there is none, as the label
- the number of hooks alongside it
Before, each entry was a plain label with a short description.
Why
This is a small visual change to the /hooks menu.
Names in the bundle/hooks
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up /hooks, on Plugin manifest reference.
If you leave one of these variables outside quotes in a shell-form command in a hooks file, `claude plugin validate` warns about it unless the hook sets [`shell`](/docs/en/hooks#command-hook-fields) to `"powershell"`.plugins/manifest-reference see the edit
Added since
A small documentation edit on Automate actions with hooks touched a line naming /hooks after this was published.
* `"type": "mcp_tool"`: call a tool on a configured MCP server. See [MCP tool hooks](/docs/en/hooks#mcp-tool-hook-fields).hooks-guide see the edit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not confirmed that this list is the one in the /hooks menu.
Anthropic's documentation agrees
A small documentation edit on Automate actions with hooks touched a line naming /hooks after this was published.
Anthropic's release notes agree
Improved lists in /help, /hooks, /copy, /chrome, /memory, /ide, /release-notes, /rewind, /diff, /remote-env, /plugin and other pickers with…