{"version":"2.1.229","anchor":"plugins-that-install-by-running-a-command-now-need-explicit-","canonical_anchor":"plugins-that-install-by-running-a-command-now-need-explicit-","heading":"Plugins that install by running a command now need explicit terminal acceptance","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/plugins-that-install-by-running-a-command-now-need-explicit-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Plugins that install by running a command now need explicit terminal acceptance\n\nPlugins that install by running a command now print it and ask you to confirm.\n\n**What**\n\nIf a plugin marketplace entry installs itself by running a command on your machine, install and update now print that command and ask \"Run this command now? [y\/N]\". Acceptance is remembered per exact command string, so a changed command forces a fresh confirmation with a warning.\n\n**Details**\n\n- `-y`\/`--yes` is refused when the CLI is itself running inside another Claude Code session.\n- In a non-interactive terminal the command is only printed, never accepted.\n- Link mode for these plugins is refused on Windows.\n\n**Usage**\n\n`claude plugin install <name>@<marketplace>` **Evidence** `Not an interactive terminal, so the command was only displayed, not accepted.`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}