Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.311,
Internal ChangesSection of the release
Unclear Which non-command hook types are now included, and what the fingerprints are used for, is not stated.
What
Hooks are commands or other actions you set up to run automatically at set points while Claude Code works. Claude Code has a step that builds an identifying fingerprint for each of your hooks. That step used to skip every hook whose type was not command. It now uses a broader test to decide which hooks to include, so a hook is no longer dropped just for being a different type.
In this step, the onFailure setting with the value block still only counts for command hooks.
Why
Hooks of other kinds, such as HTTP hooks or prompt hooks, can now be part of this step instead of always being left out.
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 doubtWhich non-command hook types are now included, and what the fingerprints are used for, is not stated.