Unclear The internal condition that lets your own hooks keep running is not stated, so it is unclear when this applies to you.
What
Hooks are commands Claude Code runs automatically at set points, such as before a tool is used. The disableAllHooks setting turns them off. Before, when it was set, Claude Code kept only the hooks your organization deploys.
Claude Code can now load hooks from your other settings files too, when all of these hold:
- An internal condition on your user settings passes.
allowManagedHooksOnlyis not in force.- No settings source other than the one that turned on
disableAllHooksalso turns it on.
Claude Code also now saves the hooks from your user settings for each session, and a hook entry can carry a personal: true marker.
Why
This changes how disableAllHooks works across your different settings files. If you rely on it to stop every hook, check that your own hooks are not still running.
Names in the bundledisableAllHooks
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The internal condition that lets your own hooks keep running is not stated, so it is unclear when this applies to you.