Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.267,
Internal ChangesSection of the release
What
When a hook (a user-configured script that runs at certain points in Claude Code) fails, the code that handles this now performs two separate steps built from a shared failure report, instead of one combined step. This applies consistently both when a hook fails during normal use and during the startup/bootstrap process.
Why
Splitting logging from reporting makes the failure-handling path clearer and more consistent between the two places it runs, though the finding does not indicate any visible change in behavior to the user.
