{"version":"2.1.248","anchor":"hooks-can-be-filtered-by-a-permission-rule-pattern","canonical_anchor":"hooks-can-be-filtered-by-a-permission-rule-pattern","heading":"Hooks can be filtered by a permission rule pattern","tier":"use","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/hooks-can-be-filtered-by-a-permission-rule-pattern","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Hooks can be filtered by a permission rule pattern\n\nHooks can carry a permission-rule matcher so they only spawn for matching tool calls.\n\n**What**\n\nA hook can now carry a matcher written in permission rule syntax, so it only fires when the tool call matches. Non-matching commands no longer spawn the hook process at all, which cuts startup cost on hooks that previously ran and immediately exited.\n\n**Details**\n\n- The field is documented as permission rule syntax, the same form used for permission allow and deny rules.\n- The stated benefit is avoiding hook spawns for commands the hook would ignore.\n\n**Evidence**\n\n`Only runs if the tool call matches the pattern. Avoids spawning hooks for non-matching commands.`\n\n- Area: Hooks\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5"}