Claude Code v2.1.236 ·
Some hook events take a separate dispatch path
Six hook events now wait on a readiness step before running; the rest are unchanged.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.236,
Internal ChangesSection of the release
Details
- The split is unconditional; there is no flag selecting between the two paths.
- What the readiness step waits for is not determined by anything in this branch.
Evidence
if (!DIw.has(e.hookInput.hook_event_name)) {
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.236 →