Troubleshoot plugins changedplugins/troubleshooting
Nearest release: v2.1.288, published 4 hours after 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 2 Oct 2026 13:58 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 2 Oct 2026 14:07 UTC.
Upstream edited
Recorded here
Lines+16added
Lines−0removed
From line
701
where the diff opens
First seen
25 Sep 2026
this site's first read of the page
Recorded edits13to this page, all time
The whole hunk
from line 701, old and new numbered
/
from line 701
701701
702702Before v2.1.246, the skills count in that summary included only a plugin's `commands/` entries, so a reload could load a plugin's `SKILL.md` skills and still report `0 skills`.
703703
704<h3 id="the-packages-it-lists-are-not-installed">
705 `The packages it lists are not installed` or `were not installed, because ...`
706</h3>
707
708`/plugin` and `claude plugin list` show one of these notes on a plugin whose dependency install left no `node_modules` directory. The plugin loads, but the parts that need the missing packages may not work.
709
710* **`are not installed`**: the install can run for this plugin but didn't finish, for example because it failed or timed out. To retry the install, run the `claude plugin update` command that the note gives, in your shell, or update the plugin from `/plugin`
711
712 ```shell theme={null}
713 claude plugin update formatter@my-marketplace
714 ```
715
716 If the retry fails, the output gives the cause. While `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` is set, `claude plugin update` and `/plugin` skip the retry and report that the plugin is at its latest version.
717
718* **`were not installed, because ...`**: the install can't run for this plugin, and the note names the reason, such as a Yarn, pnpm, or `bun.lockb` lockfile, or a lockfile whose package manager isn't installed on this computer. Updating the plugin doesn't install the packages while that reason stands. If the reason is the lockfile, the plugin's author has to replace it. If it's a missing package manager, install it, then update the plugin
719
704720<h3 id="plugin-not-cached-at">
705721 `Plugin "<name>" not cached at <path>`
706722</h3>
No line in this hunk matches that.