You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release
What
Plugins (add-on packages for Claude Code) can register hooks, which are small handlers Claude Code runs at certain moments. The default "deny" response for several of these hooks now takes a reason and passes it along with the decision. For example, a denied tool.check now gives back a decision of "deny" together with a reason.
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.
Added sinceA small documentation edit on Configure permissions touched a line naming tool.check after this was published.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 handles the [`tool.check`](/docs/en/plugins/mods/events#approve-or-refuse-a-tool-call-before-the-…permissionssee the edit
Confirmed sinceAnthropic's documentation has since written up tool.check, on Automate actions with hooks.A [mod](/docs/en/plugins/mods/overview) you install that handles `tool.check` can approve a call that your `PreToolUse` hook blocked, unless the hook is in managed settings. In plan mode, the mod can approve such a call when it's read-only…hooks-guidesee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up tool.check, on Automate actions with hooks.
Anthropic's release notes agreeAdded $.prompt.media so a prompt.submit hook of a mod installed by managed settings can read the bytes of an image or document attached to…
