{"version":"2.1.289","anchor":"plugin-hooks-modules-rollout-flag-late-load-handling-and-a","canonical_anchor":"plugin-hooks-modules-rollout-flag-late-load-handling-and-a","heading":"Startup wait for plugin hook modules reworked, including late rollout answers","tier":"internal","area":"Plugin Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289\/e\/plugin-hooks-modules-rollout-flag-late-load-handling-and-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.289","markdown":"### Startup wait for plugin hook modules reworked, including late rollout answers\n\nHow long startup waits for plugin hook modules now depends on an extra check, and a rollout answer that arrives late is logged and handled\n\n**Unclear.** The name of the rollout switch and what the new checks test are not known.\n\n**What**\n\nSome installed plugins provide hook modules, which are pieces of plugin code that run when certain events happen in Claude Code. At startup, Claude Code can wait for these modules to load. That wait has been reworked:\n\n- Whether startup waits now depends on an extra check, where before it depended on a single one.\n\n- When that extra check fails, Claude Code falls back to the older way of loading the modules.\n\n- If the rollout switch for plugin hook modules answers \"on\" after loading has already gone ahead using a saved \"off\", Claude Code now logs a message and reacts to the change.\n\n**Why**\n\nThis affects how long startup can be held up while plugin hooks load, and what happens when the rollout switch changes its answer partway through startup.\n\n- Area: Plugin Hooks\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}