{"version":"2.1.300","anchor":"hooks-module-skipped-if-judged-under-stale-policy-text","canonical_anchor":"hooks-module-skipped-if-judged-under-stale-policy-text","heading":"Hooks approved under an outdated policy are skipped","tier":"notice","area":"Hooks","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/hooks-module-skipped-if-judged-under-stale-policy-text","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Hooks approved under an outdated policy are skipped\n\nA hooks module that was approved under a different policy text than the one now in force is skipped instead of run\n\n**What**\n\nHooks are your own commands that Claude Code runs at set moments. Before, Claude Code only checked a hooks module's status. It now also checks which policy text the module was approved under. If that is not the policy currently in force, Claude Code skips the module and logs that it is passing on it.\n\n**Why**\n\nHooks now follow your organisation's current admission policy, so a change to that policy takes effect instead of older approvals carrying over.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}