What
The description for the disableAllHooks policy setting has been expanded to spell out exactly what it covers: hooks defined in settings files, hooks added by installed plugins, and statusLine execution. It now explicitly states that features built into Claude Code are not hooks in this sense and keep working, since each of those has its own separate switch.
Why
This clears up potential confusion about the scope of disableAllHooks, making clear it's a switch for custom/plugin hooks and the status line specifically, not a master switch for every Claude Code feature.
Names in the bundledisableAllHooks
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 disableAllHooks, on All settings.
| [`disableAllHooks`](#disableallhooks) | Turn off [hooks](/docs/en/hooks), a custom [status line](/docs/en/statusline), and a custom [`@` file suggestion](/docs/en/interactive-mode#quick-commands) command at once | Hooks and automation | …settings-reference see the edit
Added since
A small documentation edit on Customize your status line touched a line naming disableAllHooks after this was published.
The same trust, `disableAllHooks`, and [`allowManagedHooksOnly`](/docs/en/settings-reference#allowmanagedhooksonly) gates that apply to `statusLine` apply here. Plugins can ship a default `subagentStatusLine` in their [`settings.json`](/do…statusline see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Customize your status line touched a line naming disableAllHooks after this was published.