{"version":"2.1.323","anchor":"plugin-install-can-surface-and-print-command-source-output","canonical_anchor":"plugin-install-can-surface-and-print-command-source-output","heading":"Plugin install now flags output printed by the plugin's install command","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-install-can-surface-and-print-command-source-output","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Plugin install now flags output printed by the plugin's install command\n\nWhen a plugin's install command prints a message, Claude Code now shows a warning and quotes it, plus other \/plugin install and menu changes\n\n**What**\n\nSome 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.\n\n- 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:\".\n\n- Printed text: the result notes \"The plugin's install command printed: ...\" with the output.\n\n- 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.\n\n- `\/plugin` menu: adds the command-output notice to its messages.\n\n- `plugin install --json`: the machine-readable output gains `unsetOptionCount`.\n\n- `plugin list`: shows \"not loaded\" when a plugin has problems that are not errors.\n\n- 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.\n\n- 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.\n\n- `npm-install` view: removed from the `\/plugin` screen.\n\n- Dependency check: the check of what a plugin depends on can now skip a given set of sources.\n\n**Why**\n\nA 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.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}