What
Hooks are commands Claude Code runs automatically at certain moments, such as before a tool runs. The /hooks view, which lists them, has been reworded and gained a detail pane.
- When
disableAllHooksis set, the view is titled "Hooks" and explains in one sentence that no hook command runs, the status line isn't shown, and tools run without hook checks. It adds " Hooks set by your organization still run." when managed hooks still apply. Before, it said "Hook configuration · disabled" and "All hooks are currently disabled" with a bulleted list. - The status line reads "disabled by your organization" or "disabled", with a count of hooks not running.
- When policy restricts hooks, the view says "Only hooks from managed settings run here." and explains that user, project and local hooks are blocked and not listed, and that managed hooks are not shown either. The read-only note is shorter.
- A new detail pane for each hook shows its event, matcher, source, plugin, status message and command or script, labels "Script hook" and "MCP tool hook" types, and explains how to change it, for example "Built in to Claude Code. It can't be changed or removed." or "Set by your organization's managed settings. It can't be changed here."
Why
It is now clearer why a hook isn't firing, why a list is empty, where a hook comes from and why some can't be edited, and that organization-managed hooks keep running even when you turn hooks off.