{"version":"2.1.242","anchor":"managed-hook-skip-message-now-says-sdk-callback-hooks-still-","canonical_anchor":"managed-hook-skip-message-now-says-sdk-callback-hooks-still-","heading":"Managed hook skip message now says SDK callback hooks still run","tier":"notice","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/managed-hook-skip-message-now-says-sdk-callback-hooks-still-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Managed hook skip message now says SDK callback hooks still run\n\nThe disableAllHooks notice now says SDK callback hooks still run while configured hooks are skipped.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- The worktree message now attributes a non-running hook to an untrusted workspace or a matcher that did not match.\n- Hook invocation also passes storage and credentials through to the hook.\n\n**Evidence**\n\n`\"WorktreeCreate hook failed: hook is configured but did not run (workspace not trusted or matcher mismatch)\"`\n\n- Area: Hooks\n- Names: `disableAllHooks`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}