A process-wide switch no longer decides where plugin hook modules run first
Whether the hook modules from installed plugins go first is now decided only by managed settings, a Team or Enterprise organization, or prepended plugins
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.287,
Internal ChangesSection of the release
What
Hooks are commands that Claude Code runs on its own at set points. Installed plugins can provide hook modules, and Claude Code decides whether those modules take the outermost position, meaning they run first.
Claude Code used to skip that position when hook modules were switched off for the whole running process. That step has been removed. The position is now decided only by:
Plugins listed to go first.
Managed settings on the machine.
Belonging to a Team or Enterprise organization.
Why
Turning hook modules off for the whole process no longer stops them taking the outermost position, so the order hooks run in can differ from before.
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 doubtIt is not clear whether the removed off switch now applies somewhere else.
