Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.239 ·

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.

Use it now Improvements
JSON All of v2.1.239
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.239,
What probably matters to youSection of the release
What

claude plugin enable, disable, install, update and uninstall now refuse clearly instead of acting confusingly. Built-in plugins can only be enabled or disabled, never installed, updated or uninstalled, and a plugin locked by organization managed settings cannot be toggled for a --plugin-dir, skills directory or claude.ai-synced copy.

Details
  • Toggling a synced plugin now reports when a higher-precedence settings source would still govern it, or when --setting-sources makes the session ignore that source.
  • disable-all now writes explicit false entries for synced plugins that no settings file mentions.
Evidence

built-in plugins cannot be installed, updated or uninstalled

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

Read from
Names in the bundleclaude plugin enableclaude plugin disableclaude plugin installclaude plugin updateclaude plugin uninstall
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up claude plugin disable, on Plugins reference. * **Turn one off**: in the synced session, run `claude plugin disable <name>@synced`, or ask Claude to run it. Claude Code saves the choice as `"<name>@synced": false` in that environment's user-level [`enabledPlugins`](/docs/en/settings-r… plugins-reference see the edit
Confirmed since Anthropic's documentation has since written up claude plugin enable, on Plugins reference. * **Turn one off**: in the synced session, run `claude plugin disable <name>@synced`, or ask Claude to run it. Claude Code saves the choice as `"<name>@synced": false` in that environment's user-level [`enabledPlugins`](/docs/en/settings-r… plugins-reference see the edit
Confirmed since Anthropic's documentation has since written up claude plugin update, on Claude Code changelog. * Added `--accept-command <sha256>` to `claude plugin install` and `claude plugin update` to accept exactly the command a previous `--json` run displayed, instead of `-y` changelog see the edit
Confirmed since Anthropic's documentation has since written up claude plugin install, on Claude Code changelog. * Added `--json` to `claude plugin install`, `uninstall`, `update`, `enable` and `disable`, and `errorDetails`/`noteDetails` to each row of `claude plugin list --json` changelog see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up claude plugin install, on Claude Code changelog.

See this entry in the whole of v2.1.239 →

Feedback