Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Plugin install docs do not explain reinstall behavior for already-installed plugins or dependency repair [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52206•Fetched 2026-04-23 07:33:45
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3

Root Cause

  • rerunning plugin install on an already-installed plugin is supported
  • the command refreshes dependency resolution for plugin-declared dependencies
  • this is an appropriate recovery step when a plugin install is present but broken because a dependency was installed at the wrong version
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/plugins-reference

Section/Topic

plugin install command reference, plus the install/troubleshooting guidance for reinstalling plugins

Current Documentation

The command reference currently says:

Install a plugin from available marketplaces.

claude plugin install <plugin> [options]

Scope determines which settings file the installed plugin is added to.

The install guide currently says:

Once you've added marketplaces, you can install plugins directly (installs to user scope by default):

/plugin install plugin-name@marketplace-name

The troubleshooting section also says:

Plugin skills not appearing: Clear the cache with rm -rf ~/.claude/plugins/cache, restart Claude Code, and reinstall the plugin.

What's Wrong or Missing?

Changelog v2.1.118 includes: Fixed plugin install on an already-installed plugin not re-resolving a dependency installed at the wrong version.

The docs do not explain that rerunning /plugin install or claude plugin install against an already-installed plugin is a supported repair path, or that plugin install re-resolves plugin dependencies when the installed dependency version is wrong.

That leaves a gap between the troubleshooting advice to "reinstall the plugin" and the actual supported command behavior. A user reading the current docs cannot tell whether they should uninstall first, rerun install directly, or expect install to repair dependency mismatches.

Suggested Improvement

Add a short note under the plugin install command docs and the plugin troubleshooting guidance that explains:

  • rerunning plugin install on an already-installed plugin is supported
  • the command refreshes dependency resolution for plugin-declared dependencies
  • this is an appropriate recovery step when a plugin install is present but broken because a dependency was installed at the wrong version

An example note would be enough; this does not need a long workflow.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/plugins-referencePrimary plugin install command semantics
https://code.claude.com/docs/en/discover-pluginsUser-facing install flow and troubleshooting guidance
https://code.claude.com/docs/en/cli-referenceEntry point that sends users to plugin command docs

Total scope: 3 pages affected

Source: Changelog v2.1.118

Exact changelog entry:

Fixed plugin install on an already-installed plugin not re-resolving a dependency installed at the wrong version

extent analysis

TL;DR

Update the documentation for the plugin install command to include information about rerunning the command on an already-installed plugin to refresh dependency resolution.

Guidance

  • Add a note to the plugin install command documentation explaining that rerunning the command on an already-installed plugin is a supported way to repair dependency mismatches.
  • Clarify that the plugin install command re-resolves plugin dependencies when the installed dependency version is wrong.
  • Update the troubleshooting guidance to reflect that rerunning plugin install is an appropriate recovery step when a plugin install is present but broken due to a dependency issue.
  • Review the affected pages (plugins-reference, discover-plugins, and cli-reference) to ensure consistent documentation.

Example

A possible example note could be: "Rerunning plugin install on an already-installed plugin will refresh dependency resolution for plugin-declared dependencies, making it a useful recovery step when a plugin install is present but broken due to a dependency issue."

Notes

The suggested improvement is focused on updating the documentation to reflect the existing behavior of the plugin install command, rather than changing the command's behavior itself.

Recommendation

Apply workaround: Update the documentation to reflect the correct behavior of the plugin install command, as this will help users understand how to use the command to repair dependency mismatches.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#container setup#orchestration issue#cache issue#memory leak#API versioning

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] Plugin install docs do not explain reinstall behavior for already-installed plugins or dependency repair [1 participants]