{"version":"2.1.318","anchor":"hook-matcher-metadata-no-longer-lists-load-reason","canonical_anchor":"hook-matcher-metadata-no-longer-lists-load-reason","heading":"Instructions-loaded hook no longer lists the load reason as a match field","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/hook-matcher-metadata-no-longer-lists-load-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Instructions-loaded hook no longer lists the load reason as a match field\n\nThe hook that runs when instruction files load no longer lists `load_reason` as the field its matcher checks\n\n**Unclear.** It is not clear whether a matcher that filters on the load reason still works.\n\n**What**\n\nA hook is a command you set up to run automatically when something happens in Claude Code. One hook runs when instruction files are loaded. It can only observe and cannot block anything.\n\nA hook's matcher decides which events the hook runs for. This hook's matcher description used to name `load_reason` (why the instructions were loaded) as the field to match against. That entry has been removed.\n\n**Why**\n\nIf your hook matcher filters on `load_reason`, this may change whether it still picks out the events you expect.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}