{"version":"2.1.311","anchor":"hook-cloud-sync-accepts-non-command-hook-types","canonical_anchor":"hook-cloud-sync-accepts-non-command-hook-types","heading":"Hook fingerprinting no longer skips hooks that are not command hooks","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/hook-cloud-sync-accepts-non-command-hook-types","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Hook fingerprinting no longer skips hooks that are not command hooks\n\nA step that builds an identifying fingerprint for each hook no longer skips every hook whose type is not command\n\n**Unclear.** Which non-command hook types are now included, and what the fingerprints are used for, is not stated.\n\n**What**\n\nHooks 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.\n\nIn this step, the `onFailure` setting with the value `block` still only counts for command hooks.\n\n**Why**\n\nHooks of other kinds, such as HTTP hooks or prompt hooks, can now be part of this step instead of always being left out.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}