{"version":"2.1.301","anchor":"hook-matching-now-passes-managedhooksonly-to-a-new-check","canonical_anchor":"hook-matching-now-passes-managedhooksonly-to-a-new-check","heading":"Matched hooks now go through an extra check tied to managedHooksOnly","tier":"internal","area":"Hooks","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/hook-matching-now-passes-managedhooksonly-to-a-new-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Matched hooks now go through an extra check tied to managedHooksOnly\n\nAfter Claude Code picks which hooks apply, it now runs one more check that is told whether managedHooksOnly is set\n\n**Unclear.** What the new check does with the matched hooks, and whether it can change which hooks run, is not shown.\n\n**What**\n\nHooks are commands Claude Code runs automatically at set points, such as before or after it uses a tool. After Claude Code works out which hooks match the current moment, it now passes those hooks to an additional check, along with whether the `managedHooksOnly` option is set. Before, the matched hooks were used directly with no further step.\n\n**Why**\n\nIf you use `managedHooksOnly`, there is now one more step between matching a hook and running it.\n\n- Area: Hooks\n- Names: `managedHooksOnly`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}