You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
What
Some plugins run their own install command when you add them. If that command prints something, Claude Code now shows it to you instead of reporting a plain success.
Success message: it changes from "Successfully installed" to "Installed", uses a warning mark, and says "Its install command printed a message. Check it in case the plugin needs another step:".
Printed text: the result notes "The plugin's install command printed: ..." with the output.
Activation note: the message says the plugin is active and to check the terminal, or tells you to run /reload-plugins to activate it. The wording is now assembled from separate notes rather than fixed text.
/plugin menu: adds the command-output notice to its messages.
plugin install --json: the machine-readable output gains unsetOptionCount.
plugin list: shows "not loaded" when a plugin has problems that are not errors.
Plugin updates: a new fallback picks the newest plugin version that works with your Claude Code version, and can report that an older version was used.
Import picker: a new "Import MCP Servers from Claude Desktop" picker has a checkbox per server and adds a number to names that collide. MCP servers are programs that give Claude extra tools.
npm-install view: removed from the /plugin screen.
Dependency check: the check of what a plugin depends on can now skip a given set of sources.
Why
A plugin whose installer prints instructions may need an extra step before it works. Showing that output, with a warning, makes it harder to miss and explains why a freshly installed plugin might not behave yet.
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeAdded unsetOptionCount to the claude plugin install --json result: how many userConfig options are not yet set
