What
When you open an untrusted project, the trust dialog now says directories that may load as plugins were skipped, rather than asserting they are plugins, and points at /reload-plugins to load whichever ones qualify.
Details
- Plugin discovery validates each candidate through a check instead of reading a
.claude-plugindirectory unconditionally. - Discovery yields to the event loop between directories, so scanning a project with many candidates does not block the interface.
Evidence
that may load as ${d === 1 ? "a plugin" : "plugins"}
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.