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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

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

You'll notice
Useful3 Signal0
Plugins

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

/plugin/reload-plugins
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.

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