{"version":"2.1.288","anchor":"hooks-modules-disabled-reason-is-now-computed","canonical_anchor":"hooks-modules-disabled-reason-is-now-computed","heading":"Message about plugin hooks being off now states the actual reason","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/hooks-modules-disabled-reason-is-now-computed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Message about plugin hooks being off now states the actual reason\n\nWhen hooks are turned off for installed plugins, the message now gives the actual reason instead of always blaming a rollout switch\n\n**Unclear.** Which reasons the message can now name is not established.\n\n**What**\n\nClaude Code can turn off hooks for installed plugins while still loading its built-in plugins. Hooks are your own commands that run automatically at set moments. The message for this case used to always say that a rollout switch had turned them off. It now works out the actual reason and states that.\n\n**Why**\n\nWhen you are trying to find out why plugin hooks are not running, the message can name the real cause, such as an environment variable you set.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}