Command reference ยท Claude Code
/hooks
Shows hook configurations for tool events.
/hooks opens a read-only browser for all currently configured hooks - automated shell commands, HTTP calls, prompts, agents, or MCP tool calls that trigger at specific points in the Claude Code workflow, such as before or after a tool call. The menu lists every hook event along with the number of configured hooks, lets you expand individual matchers, and shows the full details for each hook: event, matcher, type, and the exact command, prompt text, or URL.
Each entry is also tagged with its source: User (from ~/.claude/settings.json), Project (.claude/settings.json), Local (.claude/settings.local.json), Plugin (from an installed plugin), Session (registered only for the running session), or Built-in (internal to Claude Code).
The command takes no argument and doesn't change anything - it's purely for review, for example to check why a tool call was blocked or modified.
โ WHEN TO USE IT?
Check the existing configuration before adding a new hook
Run /hooks to see whether a matcher for PreToolUse already applies to Bash commands
Trace which settings file a hook comes from
Open /hooks and check the source tag (User/Project/Local/Plugin) when a hook comes from an installed plugin
โ WHEN NOT TO?
Editing or reconfiguring hook rules
according to the docs, /hooks is a pure read-only browser, not an editing interface
Better: adjust the configuration directly in settings.json (or have it adjusted), or use the update-config skill
Finding out why a configured hook fails at runtime
/hooks only shows the configuration (event, matcher, command), not runtime errors - according to the docs, those end up in the debug log
Better: use /debug to view the session debug log with the hook error messages
SOURCES
- Claude Code docs (official) โ code.claude.com
MORE COMMANDS ยท Claude Code