{"version":"2.1.318","anchor":"notification-hook-matcher-no-longer-declares-fieldtomatch","canonical_anchor":"notification-hook-matcher-no-longer-declares-fieldtomatch","heading":"Notification hook matcher no longer names the field it matches","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/notification-hook-matcher-no-longer-declares-fieldtomatch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Notification hook matcher no longer names the field it matches\n\nThe Notification hook's matcher details no longer say it matches on `notification_type`, though its list of values stays\n\n**Unclear.** It is not clear whether `Notification` matchers match any differently now.\n\n**What**\n\nA hook is a command you set to run when something happens in Claude Code, and a matcher limits which events trigger it. The details Claude Code keeps about the `Notification` hook's matcher no longer say it matches on the `notification_type` field. The list of values it accepts, including `elicitation_complete` and `elicitation_response`, is unchanged.\n\n**Why**\n\nThis could change how the matcher is described or checked where hooks are set up.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}