{"version":"2.1.299","anchor":"plugin-hooks-modules-rollout-gating-helpers","canonical_anchor":"plugin-hooks-modules-rollout-gating-helpers","heading":"Hooks from plugins you installed yourself can be held back by a rollout switch","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/plugin-hooks-modules-rollout-gating-helpers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Hooks from plugins you installed yourself can be held back by a rollout switch\n\nHook code from plugins you installed is skipped at startup unless a remote rollout switch answers in time; organization and built-in plugins still load\n\n**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.\n\n**What**\n\nHooks 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.\n\nHooks 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.\n\n**Why**\n\nThis 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.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}