You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
What
Hooks are commands that run automatically at certain points, such as before or after a tool runs. Checking a plugin's hooks.json now warns when a command-type hook uses ${CLAUDE_PLUGIN_ROOT}, ${CLAUDE_PLUGIN_DATA} or ${CLAUDE_PROJECT_DIR} without quotes around it. These placeholders are replaced with folder paths when the hook runs. The warning suggests quoting the placeholder or using exec form. Exec form means giving the command and its arguments separately.
Exec-form hooks (those with args) and PowerShell hooks are not checked.
The warning is not behind a gate, so it applies to everyone.
Plugins are sorted by install count (the highest across installCountIds), then by plugin-directory origin, then by name.
Each marketplace has filter tabs, headed by an "All" tab.
Why
An unquoted path breaks when the folder name contains a space, which is a common cause of broken plugin hooks. The warning points plugin authors at the problem before users hit it. The new sorting puts widely installed plugins first when browsing.
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 sinceAnthropic's documentation has since written up hooks.json, 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…permissionssee the edit
Added sinceA small documentation edit on Automate actions with hooks touched a line naming hooks.json after this was published.The reverse is not true: a hook returning `"allow"` doesn't bypass deny rules from settings, and it can't suppress the prompt for MCP tools marked [`requiresUserInteraction`](/docs/en/mcp#require-approval-for-a-specific-tool) or for connec…hooks-guidesee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesA small documentation edit on Automate actions with hooks touched a line naming hooks.json after this was published.
Anthropic's release notes agreeImproved plugin hook-failure errors to name the offending plugin, and added a claude plugin validate warning when a shell-form hook leaves…
