plugin disable

A Claude Code CLI flag, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Releases whose published page names plugin disable.

1. v2.1.307 21 Oct 2026
   Built-in plugins can now explain why they can't be installed

   The error for trying to install a built-in plugin can now show a message specific to that plugin

   named in this entry

2. v2.1.268 10 Sep 2026
   Plugin CLI commands (disable, disable-all, update) gain --json output

   Plugin disable, disable-all, and update commands gain --json output alongside other plugin commands

   named in this entry

3. v2.1.247 26 Aug 2026
   claude plugin enable/disable refuses an ambiguous bare name

   Enabling or disabling an ambiguous plugin name now stops and asks you to write plugin@marketplace.

   named in this entry

4. v2.1.246 25 Aug 2026
   Plugin enable/disable no longer lose telemetry, and can target built-in plugins

   You can now enable or disable bundled built-in plugins by name from the command line.

   named in this entry

5. v2.1.239 21 Aug 2026
   Plugin commands explain why a plugin cannot be toggled

   Plugin commands now explain refusals for built-ins and org-locked plugins instead of acting oddly.

   named in this entry

No release's published evidence quotes this name. The ledger indexes the Evidence lines of every changelog on this site, so this says nobody here has ever quoted it; it says nothing about how old the name is.

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the CLI flag does. All CLI flags.