What
When the managed disableAllHooks setting is on, the skip notice now states that configured hooks are skipped while hooks supplied as SDK callbacks still run, instead of implying all hooks are off. The worktree-creation failure message no longer lists disableAllHooks as a possible cause.
Details
- The worktree message now attributes a non-running hook to an untrusted workspace or a matcher that did not match.
- Hook invocation also passes storage and credentials through to the hook.
Evidence
"WorktreeCreate hook failed: hook is configured but did not run (workspace not trusted or matcher mismatch)"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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 MCP, plugins, skills, and hooks.
Claude Code [managed settings](/docs/third-party/claude-desktop/code#interaction-with-claude-code%E2%80%99s-own-managed-settings) deployed on the device govern these hooks as they do in the Claude Code CLI: `disableAllHooks` turns them off…third-party/claude-desktop/extensions see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up disableAllHooks, on MCP, plugins, skills, and hooks.