Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.163 Home All releases ←olderv2.1.140 v2.1.165newer→
Claude Code v2.1.163

/plugin list --enabled and --disabled Filters

What

The /plugin list command now accepts --enabled and --disabled flags to filter the output to only installed plugins matching the requested state.

Usage
/plugin list --enabled    # show only enabled plugins
/plugin list --disabled   # show only disabled plugins
/plugin list              # show all installed plugins (unchanged)
Details
  • Enabled/disabled status is shown as ✓ enabled or ✗ disabled per plugin entry.
  • If no plugins match the filter, a short message like "No disabled plugins." is shown.
  • Plugin entries also show version and scope where available.
  • A pending-reload indicator — run /reload-plugins to apply appears when the in-memory state differs from what would be loaded on next start.
Evidence

Filter flag in command rendering (search for "/plugin list [--enabled|--disabled] - List installed plugins")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.163 →