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.239 Home All releases ←olderv2.1.238 v2.1.240newer→
Claude Code v2.1.239

Plugin commands explain why a plugin cannot be toggled

Use it now
Useful3 Signal2
Plugins

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

claude plugin enableclaude plugin disableclaude plugin installclaude plugin updateclaude plugin uninstall
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.

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.239 →