{"version":"2.1.265","anchor":"non-pretooluse-hooks-can-be-routed-through-a-new-classic-h","canonical_anchor":"non-pretooluse-hooks-can-be-routed-through-a-new-classic-h","heading":"Non-PreToolUse hooks can be routed through a new 'classic' hook chain","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/non-pretooluse-hooks-can-be-routed-through-a-new-classic-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Non-PreToolUse hooks can be routed through a new 'classic' hook chain\n\nNon-PreToolUse hooks can now be routed through a separate 'classic' hook execution chain\n\n**Unclear.** What determines whether an event is gated as a 'classic' hook, and what practical difference this makes for hook authors, isn't specified.\n\n**What**\n\nClaude Code's main hook-execution logic now checks, for hook events other than `PreToolUse` (which runs before a tool call executes and can block it), whether the event is gated as a \"classic\" hook. If so, it delegates to a separate function that runs managed and plugin hook handlers on their own and merges the results back in, then re-enters the main hook logic marked as part of that classic chain.\n\n**Why**\n\nThis adds a distinct execution path for certain hook events, letting managed and plugin hooks be processed separately before being merged with normal hook results.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}