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

Claude Code v2.1.221 ·

Batch plugin install distinguishes disabled-by-default from disabled-in-settings

Batch plugin installs now tell you which plugins are off by default versus off in your settings.

You'll notice Improvements
JSON All of v2.1.221
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.221,
ImprovementsSection of the release
What

The multi-plugin install summary tells you why each installed plugin is not running, and the closing line counts only the plugins that actually came up.

Details
  • Two separate lists: " Disabled by default — enable in /plugin: " for manifest defaults and " Disabled in your settings: " for the user's own settings.
  • The active count decides between "Plugins are now active.", "Run /reload-plugins to activate." and " Some plugins couldn't be loaded — see /plugin for details.".
  • The single-plugin screen carries matching installedDisabled and installedDisabledByDefault view-state fields, derived from the enabledPlugins setting and manifest.defaultEnabled.
Evidence

Disabled in your settings:

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

Read from
Names in the bundle/plugin/reload-plugins
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeChanged /plugin install to refresh a stale marketplace catalog and retry before reporting a plugin not found

See this entry in the whole of v2.1.221 →

Feedback