What
- Plugin loading now produces clearer diagnostics when something goes wrong reading a plugin's component folders: checking each default folder (commands/agents/skills/output-styles/themes/workflows) now logs an error and records a diagnostic entry when the failure is something other than "not found", instead of silently treating the folder as absent.
- When a plugin or marketplace manifest path can't be found and there's an associated system error number (errno), the error message now includes that errno and suggests likely causes, such as a self-referential symlink, a broken network mount, or a permissions problem, and tells the user to run
/reload-plugins.
Why
These changes make it much easier to diagnose why a plugin failed to load, by surfacing the actual underlying filesystem error instead of just treating any failure as a missing file.
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.