{"version":"2.1.305","anchor":"plugin-hooks-module-load-can-be-refused-with-a-reason","canonical_anchor":"plugin-hooks-module-load-can-be-refused-with-a-reason","heading":"Blocked plugin hooks now say why they were refused","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/plugin-hooks-module-load-can-be-refused-with-a-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Blocked plugin hooks now say why they were refused\n\nWhen Claude Code refuses to load a plugin's hooks, the error now carries the reason it was refused\n\n**What**\n\nHooks are commands a plugin runs at set points while Claude Code works. Before loading a plugin's hooks, Claude Code runs a check. That check now returns a reason, and if it does, the load fails with that reason attached to the error. Before, the check only answered yes or no, and the error named only the plugin.\n\n**Why**\n\nWhen a plugin's hooks are blocked, the error can now explain why instead of only saying which plugin it was.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}