What
Hooks 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.
- Before, it said the feature was early access and that you had to set
CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1to load it. - Now it says hooks modules are off because
CLAUDE_CODE_ENABLE_FUNCTION_HOOKSis 0 in a settings file or in the environment, or because "the rollout switch served off". - The name
CLAUDE_CODE_ENABLE_FUNCTION_HOOKSnow appears 12 times in the code, up from 9.
The code that decides the default was not examined, so it is not confirmed that hooks modules are now on by default.
Why
The 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The message wording suggests hooks modules are now on by default, but that default has not been confirmed.