Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.265,
Internal ChangesSection of the release
Unclear What determines whether an event is gated as a 'classic' hook, and what practical difference this makes for hook authors, isn't specified.
What
Claude 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.
Why
This adds a distinct execution path for certain hook events, letting managed and plugin hooks be processed separately before being merged with normal hook results.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat determines whether an event is gated as a 'classic' hook, and what practical difference this makes for hook authors, isn't specified.
