What
When a cloud session reports no loaded plugin count, the notice now says the plugins were sent but not confirmed and points at /reload-plugins, instead of reporting success.
Details
- The success check was tightened: a null loaded count no longer counts as loaded, where before
e.loaded === null || e.loaded >= npassed. - In that case the message is raised from debug level to a visible notice, and the "applies from your next prompt" tail is hedged.
Evidence
it has not confirmed them — /reload-plugins shows what loaded.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/reload-plugins
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Push events into a running session with channels touched a line naming /reload-plugins after this was published.
When the install asks for an installation scope, choose the user scope option so the plugin is available across all your projects. Check the install summary: if it reports `Run /reload-plugins to activate.`, see [Apply plugin changes witho…channels see the edit
Confirmed since
Anthropic's documentation has since written up /reload-plugins, on Claude Code changelog.
* Improved `/plugin`: installing, enabling or disabling a plugin now takes effect when you close the menu; `/reload-plugins` is no longer needed afterwardschangelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /reload-plugins, on Claude Code changelog.