Troubleshoot plugins changedplugins/troubleshooting
Nearest release: v2.1.290, published 4 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 5 Oct 2026 22:35 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 5 Oct 2026 22:37 UTC.
Upstream edited
Recorded here
Lines+4added
Lines−4removed
From line
683
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits20to this page, all time
The whole hunk
from line 683, old and new numbered
/
from line 683
683683* **A plugin someone else published**: open **Installed** in `/plugin` and open the plugin's details pane, which lists what the plugin contains. A plugin that lists no skills there has none to offer when you type `/`
684684
685685<h3 id="run-reload-plugins-to-activate">
686 `Run /reload-plugins to activate.`
686 `Run /reload-plugins to apply.`
687687</h3>
688688
689The install summary in `/plugin` ended with `Run /reload-plugins to activate.` instead of `Plugin is now active.`
689The install summary in `/plugin` ended with `Run /reload-plugins to apply.` instead of `Plugin is now active.` A `Plugins changed. Run /reload-plugins to activate.` notice can appear above the prompt at the same time.
690690
691691Claude Code didn't activate the plugin during the install, either because activating it would [invalidate the prompt cache](/docs/en/prompt-caching#enabling-or-disabling-a-plugin) or because the activation attempt failed.
692692
No line in this hunk matches that.