Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Plugin management docs omit `plugin prune` and `plugin uninstall --prune` [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#54159•Fetched 2026-04-29 06:34:43
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3

Code Example

claude plugin prune

---

claude plugin uninstall formatter@your-org --prune
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

plugin uninstall in the CLI plugin management reference, plus the missing plugin prune command documentation

Current Documentation

The command reference currently says:

plugin uninstall

Remove an installed plugin. claude plugin uninstall <plugin> [options]

Options: | -s, --scope <scope> | Uninstall from scope: user, project, or local | | --keep-data | Preserve the plugin's persistent data directory |

The end-user plugin guide currently says:

Completely remove a plugin: /plugin uninstall plugin-name@marketplace-name

The dependency guide documents automatic dependency installation, but not cleanup:

When you install a plugin that declares dependencies, the install output lists which dependencies were auto-installed alongside it.

No documentation currently exists for claude plugin prune.

What's Wrong or Missing?

Changelog v2.1.121 added claude plugin prune to remove orphaned auto-installed plugin dependencies and added cascading cleanup via claude plugin uninstall --prune.

The current docs are behind that behavior in two places:

A. Missing new command

There is no documented plugin prune command in the plugin command reference or user-facing plugin management guide.

B. Outdated uninstall options

The plugin uninstall reference still lists only --scope and --keep-data, so it does not tell users that uninstall can now cascade dependency cleanup with --prune.

C. Missing cleanup guidance for auto-installed dependencies

The docs explain that dependencies can be auto-installed, but they do not explain how users should remove orphaned auto-installed dependencies after uninstalling a plugin.

Suggested Improvement

Update the plugin management docs to cover the new cleanup workflow introduced in v2.1.121:

  1. Add a ### plugin prune subsection to the CLI reference with syntax, a short description, and at least one example:
claude plugin prune
  1. Add --prune to the plugin uninstall options table and include an example such as:
claude plugin uninstall formatter@your-org --prune
  1. In the user-facing plugin installation/management docs, add a short explanation of when to use plugin prune versus plugin uninstall --prune, and define what counts as an orphaned auto-installed dependency.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/plugins-referencePrimary CLI command reference; lists plugin uninstall options but has no plugin prune section
https://code.claude.com/docs/en/discover-pluginsUser-facing plugin management guide; shows uninstall commands but not pruning orphaned auto-installed dependencies
https://code.claude.com/docs/en/plugin-dependenciesExplains auto-installed plugin dependencies but not how to clean up orphaned ones

Total scope: 3 pages affected

Source: Changelog v2.1.121

Exact changelog entry:

Added claude plugin prune to remove orphaned auto-installed plugin dependencies; plugin uninstall --prune cascades

extent analysis

TL;DR

Update the plugin management documentation to include the new plugin prune command and the --prune option for plugin uninstall.

Guidance

  • Add a ### plugin prune subsection to the CLI reference with syntax, description, and example.
  • Update the plugin uninstall options table to include --prune and provide an example.
  • Explain the difference between plugin prune and plugin uninstall --prune in the user-facing plugin management guide.
  • Define what constitutes an orphaned auto-installed dependency in the documentation.

Example

claude plugin prune
claude plugin uninstall formatter@your-org --prune

Notes

The current documentation is outdated and missing crucial information about the new cleanup workflow introduced in v2.1.121. Updating the documentation will help users understand how to properly remove orphaned auto-installed dependencies.

Recommendation

Apply workaround: Update the documentation to reflect the new plugin prune command and --prune option for plugin uninstall, as this will provide users with the necessary information to manage plugins effectively.

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…
#installation#prompt issue#agent setup#task chaining#parallel task

Still need to ship something?

×6

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

Back to top recommendations

TRENDING