The untrusted-project dialog no longer overstates skipped plugins and points at /reload-plugins.
What's wrong with this entry?
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.
- 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.
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.
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.221
Plugin install now tells you when the plugin failed to load
Both mention reload
-
v2.1.242
/reload-plugins now warns about LSP tool changes too
Both mention reload