{"version":"2.1.229","anchor":"plugins-installed-by-running-a-command-gain-a-link-mode-and-","canonical_anchor":"plugins-installed-by-running-a-command-gain-a-link-mode-and-","heading":"Plugins installed by running a command gain a link mode and clearer consent errors","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/plugins-installed-by-running-a-command-gain-a-link-mode-and-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Plugins installed by running a command gain a link mode and clearer consent errors\n\nCommand-installed plugins can be symlinked instead of copied, and consent errors say what changed.\n\n**What**\n\nA marketplace entry that installs a plugin by running a command on your machine can now use `mode: \"link\"`, where the directory the command produces is symlinked in place instead of copied. Link mode is refused on Windows. If the marketplace's command changed since you accepted it, the refusal now says specifically what changed, and the \/plugin details pane shows the command and its mode.\n\n**Details**\n\n- the install record keeps the path the command produced and the paths previous runs produced, so a changed producer path is detectable\n- consent is tied to the exact command text you approved\n\n**Evidence**\n\n`Installed by running a command on this machine:`\n\n- Area: Plugins\n- Names: `\/plugin`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}