What
Hooks are commands that Claude Code runs automatically at set moments. The notes in the hooks screen that explain where each hook comes from are now full sentences. For example, a hook from a plugin now reads: "This hook comes from a plugin and stops running when that plugin is disabled (/plugin)."
Why
Only the wording changed; the hooks behave as before.
Names in the bundle/plugin
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 /plugin, on Configure permissions.
That precedence covers hooks in settings files and in a plugin's `hooks/hooks.json`. A [mod](/docs/en/plugins/mods/overview) you install that hooks `tool.check` answers after the rules and the `PreToolUse` hooks have decided, and its answe…permissions see the edit
Added since
A small documentation edit on Explore the .claude directory touched a line naming /plugin after this was published.
| `dev-mods/<session>/` | [Mods that Claude wrote](/docs/en/plugins/mods/create#ask-claude-for-a-mod) during the session |claude-directory see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Explore the .claude directory touched a line naming /plugin after this was published.
Anthropic's release notes agree
Fixed /plugin's Discover tab showing a marketplace name unquoted in its "Checking … for new plugins" line when its rows already show that…