What
Some 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:
- Whether startup waits now depends on an extra check, where before it depended on a single one.
- When that extra check fails, Claude Code falls back to the older way of loading the modules.
- 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.
Why
This 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The name of the rollout switch and what the new checks test are not known.