Plugin auto-updates can now apply mid-session instead of always asking you to reload.
What's wrong with this entry?
After a background auto-update, Claude Code tries to re-resolve plugin commands in the running session. The notification now says "reloaded for this session", or "reloaded with errors — see /plugin", and only falls back to the old "Run /reload-plugins to apply" when the reload was skipped or failed.
- Reload is skipped when it would invalidate caches; failures fall back rather than leaving the session in a half-updated state.
- Plugins held at a fixed version report as blocked by the pin instead of updating.
- Outcomes counted under
plugin_command_reresolve_reloadwith reasonscache_impact,load_errorsandrefresh_failed.
plugin-autoupdate-reloaded, reloaded with errors — see /plugin
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.221
Installed plugins activate in place instead of waiting for /reload-plugins
Both mention reload
-
v2.1.239
Skipped-plugin warning no longer overstates what it found
Both mention reload
-
v2.1.242
/reload-plugins now warns about LSP tool changes too
Both mention reload