What
If 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.
Details
- The prompt reads "Fetching this plugin's archive sends helper-minted headers to" followed by the destination.
- Autoupdate records a deferred error instead of running the helper.
- Managed policy can refuse the helper outright.
- Applies to every plugin declaring such a helper; there is no flag.
Evidence
Fetching this plugin's archive sends helper-minted headers to
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on Commands touched a line naming --yes after this was published.
| `/import [codex\|gemini\|cursor] [--dry-run] [--yes]` | Bring configuration from OpenAI Codex, Google Gemini CLI, or Cursor on your machine into Claude Code, including instruction files, MCP servers, commands, subagents, and skills. In […commands see the edit
Confirmed since
Anthropic's documentation has since written up --yes, on Plugins reference.
| `-y, --yes` | Skip the `--prune` confirmation prompt. Required when stdin or stdout is not a TTY | |plugins-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up --yes, on Plugins reference.