Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

Hooks modules message no longer calls the feature early access

The message shown when plugin hooks modules are off now blames CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=0 or a rollout switch, not early access

Group of 2 You'll notice Improvements
JSON All of v2.1.286
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Claude TestArea: what it touches
ImprovementsKind: in v2.1.286,
ImprovementsSection of the release

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=1 to load it.
  • 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".
  • The name CLAUDE_CODE_ENABLE_FUNCTION_HOOKS now 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.

Read from
What the documentation says
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether hooks modules are actually on by default now when nothing is set.

See this entry in the whole of v2.1.286 →

Feedback