Hooks reference changedhooks
Nearest release: v2.1.287, published 5 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 1 Oct 2026 22:23 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 1 Oct 2026 22:37 UTC.
Upstream edited
Recorded here
Lines+6added
Lines−12removed
From line
689
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits74to this page, all time
The whole hunk
from line 689, old and new numbered
/
from line 689
689689
690690### The `/hooks` menu
691691
692Type `/hooks` in Claude Code to open a read-only browser for your configured hooks. The menu shows every hook event with a count of configured hooks, lets you drill into matchers, and shows the full details of each hook handler. Use it to verify configuration, check which settings file a hook came from, or inspect a hook's command, prompt, or URL.
692Type `/hooks` in Claude Code to open a read-only browser for your configured hooks. The list labels each hook with where it comes from, such as user settings, project settings, local settings, a plugin, or the current session.
693693
694The menu displays all five hook types: `command`, `prompt`, `agent`, `http`, and `mcp_tool`. Each hook is labeled with a `[type]` prefix and a source indicating where it was defined:
694Select a hook to see the full text of what it runs and where it's defined, such as the path of its settings file or the name of its plugin.
695695
696* `User Settings`: from `~/.claude/settings.json`
697* `Project Settings`: from `.claude/settings.json`
698* `Local Settings`: from `.claude/settings.local.json`
699* `Plugin Hooks`: from a plugin's `hooks/hooks.json`
700* `Session Hooks`: registered in memory for the current session
696To browse all hook events, including ones with no hooks configured, select `All events` at the end of the list.
701697
702Selecting a hook opens a detail view showing its event, matcher, type, source file, and the full command, prompt, or URL. The menu is read-only: to add, modify, or remove hooks, edit the settings JSON directly or ask Claude to make the change.
703
704698### Disable or remove hooks
705699
706To remove a hook, delete its entry from the settings JSON file.
700To remove a hook defined in a settings file, delete its entry from that file.
707701
708702To temporarily disable all hooks without removing them, set `"disableAllHooks": true` in your settings file. Claude Code reads the value left after [settings precedence](/docs/en/settings#settings-precedence) applies, so a `"disableAllHooks": false` in a project's `.claude/settings.json` overrides a `true` in your user settings. To turn hooks off for one run whatever the project's settings say, pass `--settings '{"disableAllHooks": true}'`, which takes precedence over project and local settings. There is no way to disable an individual hook while keeping it in the configuration.
709703
No line in this hunk matches that.