{"version":"2.1.238","anchor":"plugins-that-run-a-local-command-to-fetch-their-archive-now-","canonical_anchor":"plugins-that-run-a-local-command-to-fetch-their-archive-now-","heading":"Plugins that run a local command to fetch their archive now ask first","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/plugins-that-run-a-local-command-to-fetch-their-archive-now-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Plugins that run a local command to fetch their archive now ask first\n\nPlugins that mint headers via a local command now ask you to confirm; `-y` is ignored in-session.\n\n**What**\n\nIf a plugin fetches its archive using headers minted by a local helper command, installing or updating it now shows the exact command and destination and waits for confirmation. Non-interactive runs are recorded as \"unconfirmed\" and abort. Inside a Claude Code session, `-y`\/`--yes` is ignored and you are told to run the install in your own terminal. Autoupdate never runs the helper at all.\n\n**Details**\n\n- The prompt reads \"Fetching this plugin's archive sends helper-minted headers to\" followed by the destination.\n- Autoupdate records a deferred error instead of running the helper.\n- Managed policy can refuse the helper outright.\n- Applies to every plugin declaring such a helper; there is no flag.\n\n**Evidence**\n\n`Fetching this plugin's archive sends helper-minted headers to`\n\n- Area: Plugins\n- Names: `-y`, `--yes`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 4\/5"}