{"version":"2.1.290","anchor":"a-hook-pattern-named-with-the-reserved-prefix-is-now-reporte","canonical_anchor":"a-hook-pattern-named-with-the-reserved-prefix-is-now-reporte","heading":"Warning when a hook pattern starts with a reserved prefix","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/a-hook-pattern-named-with-the-reserved-prefix-is-now-reporte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Warning when a hook pattern starts with a reserved prefix\n\nClaude Code now warns that a hook pattern starting with a reserved prefix will never run\n\n**Unclear.** The reserved prefix itself is not identified.\n\n**What**\n\nHooks are your own scripts that Claude Code runs at set moments. Each hook is registered with a pattern that decides when it fires. Claude Code now checks these patterns, and when one starts with a reserved prefix it shows a warning: \"that name cannot be a noun, so this hook is never run\". A single `!` at the start of the pattern is ignored for this check, so `!` followed by the reserved prefix triggers the same warning.\n\n**Why**\n\nBefore this check, a hook named this way simply never ran, with nothing telling you why. If you write hooks, the warning now points you to the pattern that needs renaming.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}