Cmd. /plugin
Browse, install, enable, or disable plugins.
Written and reviewed by Eric Han · Co-founder & CTO, reopt
Key takeaways
- Browse, install, enable, or disable plugins.
- Check the input surface and availability before using the examples below.
Purpose
Browse, install, enable, or disable plugins.
/plugin [subcommand]Availability
| Field | Value |
|---|---|
| Input surface | Running CLI prompt |
| Kind | Built-in |
| Status | Current reference |
| Aliases | — |
| Documented minimum | Not specified |
| Reviewed against | 2026-10-23 · Claude Code 2.1.308 |
The installed command menu and account or organization settings determine availability.
Examples
/plugin listEffects and persistence
Changes plugin installation or enabled state. The install summary reports whether activation is immediate or a reload is needed.
Cautions
Read the install summary to see whether the plugin activated immediately or requires /reload-plugins. claude plugin configure <plugin> (v2.1.285+) shows a plugin's options and which are unset, or saves values read from stdin with --values-stdin. From v2.1.286, plugin installs refuse npm sources that are git repositories or folders. v2.1.287 adds Claude Mods, plugins that can modify deeper behavior; the built-in /plugin-authoring skill is the reference for writing one. From v2.1.292, claude plugin install --marketplace <source> adds the marketplace if needed, under the same policy checks as claude plugin marketplace add, then installs the plugin from it.