Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

The /hooks menu now opens on a list of your hooks

/hooks now opens on a list of every configured hook with its event, source, command and matcher, with the event list one step away

Use it now Improvements
JSON All of v2.1.286
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
HooksArea: what it touches
ImprovementsKind: in v2.1.286,
What probably matters to youSection of the release
What

Hooks are commands that run automatically at certain moments, such as when Claude uses a tool. The first screen of /hooks is now a list of every hook you have, grouped under its event, showing:

  • where the hook comes from
  • the command it runs
  • its matcher, the rule that chooses which tools it applies to

An All events row opens the old list of events, now titled Hook events. Pressing Esc from a hook you opened from the list returns you to the list. When you have no hooks, the subtitle reads no hooks yet, or managed hooks only if your organization set them.

Before, /hooks opened on the list of events with a count of hooks for each. The menu is still read-only: to add or change a hook, edit settings.json or ask Claude.

Why

You see all your hooks at once instead of opening each event to find them.

Read from
Names in the bundle/hooks
Since it was published

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 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 Automate actions with hooks touched a line naming /hooks 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-guide see 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 after this was published.
Anthropic's release notes agreeImproved /hooks: the closing line of a hook's detail screen now says "this hook" instead of "it"

See this entry in the whole of v2.1.286 →

Feedback