{"version":"2.1.286","anchor":"hooks-module-disabled-message-now-says-it-is-on-by-default-u","canonical_anchor":"hooks-modules-test-error-now-says-it-is-controlled-by-claude","heading":"Hooks modules message no longer calls the feature early access","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/hooks-module-disabled-message-now-says-it-is-on-by-default-u","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Hooks modules message no longer calls the feature early access\n\nThe message shown when plugin hooks modules are off now blames `CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=0` or a rollout switch, not early access\n\n**Unclear.** The message wording suggests hooks modules are now on by default, but that default has not been confirmed.\n\n**What**\n\nHooks modules let installed plugins run their own code at set points while Claude Code works. When they are off, Claude Code shows a message explaining why, including when you run a plugin's tests. That message changed.\n\n- Before, it said the feature was early access and that you had to set `CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1` to load it.\n\n- Now it says hooks modules are off because `CLAUDE_CODE_ENABLE_FUNCTION_HOOKS` is 0 in a settings file or in the environment, or because \"the rollout switch served off\".\n\n- The name `CLAUDE_CODE_ENABLE_FUNCTION_HOOKS` now appears 12 times in the code, up from 9.\n\nThe code that decides the default was not examined, so it is not confirmed that hooks modules are now on by default.\n\n**Why**\n\nThe new wording suggests hooks modules may now be on unless you turn them off, with a switch controlled remotely on top. If you want them off, the message now points to setting `CLAUDE_CODE_ENABLE_FUNCTION_HOOKS` to 0.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 3\/5"}