[DOCS] `/plugin list` command and `--enabled`/`--disabled` filters are missing from plugin management docs
Documentation Type
Missing documentation (feature not documented)
Documentation Location
https://code.claude.com/docs/en/discover-plugins
Section/Topic
Manage installed plugins, the direct command examples, and the /plugin command documentation for listing installed plugins by state
Current Documentation
The plugin management guide currently says:
Run/pluginand go to the Installed tab to view, enable, disable, or uninstall your plugins. The list is grouped by scope and sorted so you see problems first: plugins with load errors or unresolved dependencies appear at the top, followed by your favorites, with disabled plugins folded behind a collapsed header at the bottom. From the list you can: pressfto favorite or unfavorite the selected plugin type to filter by plugin name or description * press Enter to open a plugin's detail view and enable, disable, or uninstall it You can also manage plugins with direct commands. ``shell /plugin disable plugin-name@marketplace-name``shell /plugin enable plugin-name@marketplace-name``shell /plugin uninstall plugin-name@marketplace-name``
The commands index currently says:
| /plugin | Manage Claude Code plugins |
The plugin reference currently documents only the shell command surface:
### plugin list List installed plugins with their version, source marketplace, and enable status. ``bash claude plugin list [options]`**Options:** |--json| Output as JSON | | |--available| Include available plugins from marketplaces. Requires--json` | |
What's Wrong or Missing?
The live docs explain how to browse the Installed tab and how to enable, disable, or uninstall plugins, but they do not document the new REPL command added in v2.1.163:
Added/plugin listcommand to list installed plugins, with--enabled/--disabledfilters
That leaves one documentation gap with three visible symptoms:
A. /plugin list itself is undocumented
No current code.claude.com page tells users they can list installed plugins directly from the slash-command surface instead of navigating the Installed tab.
B. The new state filters are undocumented
No current page documents --enabled or --disabled, so users cannot discover how to narrow the listing to only enabled or only disabled plugins.
C. The existing reference points to a different command surface
plugins-reference documents claude plugin list, but that is a shell command. It does not cover the new /plugin list slash command or explain how its new filters relate to the existing CLI command.
Suggested Improvement
Add /plugin list to the plugin management docs where users already learn the other /plugin commands.
Suggested minimum fix:
/plugin list
/plugin list --enabled
/plugin list --disabled
Add one short explanation that /plugin list shows installed plugins and that --enabled and --disabled filter the output by plugin state.
Then update one reference page so the slash-command surface is discoverable outside the install guide:
- Expand the
/pluginentry inhttps://code.claude.com/docs/en/commandsto mentionlist. - Or add a short subsection in
https://code.claude.com/docs/en/discover-pluginslisting the common/pluginsubcommands, includinglist.
If /plugin list intentionally mirrors claude plugin list, add a short cross-reference so readers know when to use the slash command versus the shell command.
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/discover-plugins | 287-324 | The installed-plugin management section documents /plugin disable, /plugin enable, and /plugin uninstall, but not /plugin list or its --enabled/--disabled filters |
| https://code.claude.com/docs/en/commands | 98 | /plugin is listed only as a generic plugin-management command, with no discoverable list subcommand |
| https://code.claude.com/docs/en/plugins-reference | 1013-1027 | The reference documents claude plugin list with --json and --available, but not the new /plugin list slash command or its state filters |
Total scope: 3 pages affected
Version context: The missing behavior was added in v2.1.163.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗