/hooks
A Claude Code slash command, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
View hook configurations for tool events
Anthropic's own wording. Read off Commands, captured 2026-09-28.
In the changelogs
22Releases whose published page names /hooks.
-
v2.1.300
Hook errors caused by Claude Code itself no longer send you to /hooks
When an internal fault stops Claude Code from finding the hooks for a call, the message now says nothing in the session can fix it
found in this entry's text
-
v2.1.287
/hooksexplains hooks that are not registered right now/hookscan now mark a hook as not registered right now and tell you to reopen/hooksto check againfound in this entry's text, named in this entry
-
v2.1.287
Shorter, clearer question about running your hooks for cloud sessions
The prompt asking whether this machine's hooks run for cloud sessions is shorter, points to
/hooksand warns hooks here can't block commands therefound in this entry's text
-
v2.1.286
The /hooks menu now opens on a list of your hooks
/hooksnow opens on a list of every configured hook with its event, source, command and matcher, with the event list one step awayfound in this entry's text, named in this entry
-
v2.1.283
The
/hooksmatcher list shows sources, matcher and hook count in columnsEach matcher in the /hooks menu now shows a dimmed source badge, the matcher or "(all)", and its hook count as separate parts of a list row
found in this entry's text, named in this entry
-
v2.1.282
Settings skill stops sending you to
/hookswhere that menu is missingWhen the
/hooksmenu is not available, the settings skill now tells you to start a new session or check the settings file insteadfound in this entry's text, named in this entry
-
v2.1.281
New hook detail view in /hooks explains where each hook comes from
/hooks now has a detail view for each hook showing where it came from and how, or whether, you can change it
found in this entry's text, named in this entry
-
v2.1.281
Rewritten 'hooks disabled' screen
The /hooks screen shown when all hooks are disabled now explains what that turns off
found in this entry's text, named in this entry
-
v2.1.281
Hooks menu policy notice reworded
When policy restricts hooks, /hooks now says only managed-settings hooks run and explains which hooks are hidden
found in this entry's text, named in this entry
-
v2.1.269
New control-channel request: list_permission_rules
New control-channel request list_permission_rules exposes the same rules shown by /permissions
found in this entry's text
-
v2.1.269
New headless-control schema: list_permission_rules
Headless control API adds list_permission_rules to expose /permissions data programmatically
found in this entry's text
-
v2.1.251
New PreModelSwitch and PostModelSwitch hooks
New PreModelSwitch and PostModelSwitch hooks let you gate or annotate every model change.
found in this entry's text
-
v2.1.247
Device-hooks consent gains a distrusted outcome when the saved answer's file cannot be checked
If your saved hooks-sharing answer can't be verified, you're asked to decide again in /hooks.
named in this entry, found in this entry's text
-
v2.1.247
Hook inventory sent to a cloud worker includes the repo root
The hook list sent to a cloud session now includes your repo root and a composed shell prefix.
found in this entry's text
-
v2.1.247
Stricter vetting of hooks forwarded to a cloud session
Hooks forwarded to a cloud session are vetted harder, and refused if their program lives somewhere the session can write.
found in this entry's text
-
v2.1.246
Cloud sessions can run this machine's hooks, once you have agreed locally
Cloud sessions can run your local hooks once you agree on this machine; run /hooks to decide.
named in this entry, found in this entry's text
-
v2.1.246
Clearer warning when a saved hooks answer cannot be reused in a cloud session
The warning about a set-aside hooks decision in a cloud session is now one short line pointing at /hooks.
named in this entry, found in this entry's text
-
v2.1.242
A planner deciding, hook by hook, what a cloud session gets, plus a /hooks panel for it
A planner decides which of your hooks a cloud session gets, with a /hooks panel to review it.
named in this entry, found in this entry's text
-
v2.1.242
Per-machine decision about whether cloud sessions may run your hooks
A Hooks settings row lets you decide whether cloud sessions may run this machine's hooks.
named in this entry
-
v2.1.219
New DirectoryAdded hook event
You can now run a hook whenever a directory is added mid-session, including via /add-dir.
named in this entry, found in this entry's text
-
v2.1.76
Built-in Hooks
found in this entry's text
-
v2.1.76
Hooks UI Redesigned as Read-Only Viewer
found in this entry's text
First cited
4The earliest release whose published evidence quoted /hooks was v2.1.246, 25 Aug 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the slash command does. All slash commands.