Hooks from plugins you installed yourself can be held back by a rollout switch
Hook code from plugins you installed is skipped at startup unless a remote rollout switch answers in time; organization and built-in plugins still load
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release
Unclear The name of the rollout switch and what it falls back to are not known, so it is unclear whether your own plugin hooks run by default.
What
Hooks are small pieces of code a plugin runs at set points while Claude Code works. Claude Code now decides whether to load the hook code of plugins you installed yourself based on a rollout switch sent from the server. If that switch has not answered within the time Claude Code waits while starting, those hooks are skipped for that run.
Hooks from plugins your organization provides, and from plugins built into Claude Code, still load either way. Claude Code also reports a status saying that hooks you installed are waiting for the rollout switch.
Why
This decides whether the hooks of your own plugins run at all when a session starts. If a plugin hook you rely on seems not to fire, this is a place to look.
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 doubtThe name of the rollout switch and what it falls back to are not known, so it is unclear whether your own plugin hooks run by default.
