{"version":"2.1.269","anchor":"new-cli-flags-for-the-plugin-eval-command-trust-plugin-an","canonical_anchor":"new-cli-flags-for-the-plugin-eval-command-trust-plugin-an","heading":"New CLI flags for the plugin-eval command: --trust-plugin and --allow-real-servers","tier":"use","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-cli-flags-for-the-plugin-eval-command-trust-plugin-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New CLI flags for the plugin-eval command: --trust-plugin and --allow-real-servers\n\n`claude plugin eval` adds `--trust-plugin` for CI and `--allow-real-servers` to run real MCP servers without mocks\n\n**What**\n\nThe plugin evaluation command gains two new flags:\n\n- `--trust-plugin`: skips the first-run trust prompt, meant for use in CI (continuous integration) pipelines, similar in spirit to `--dangerously-skip-permissions`\n\n- `--allow-real-servers`: when combined with `--mocks record`, lets a plugin's real MCP server processes start and run for any servers that have no mock available, running outside Claude Code's OS sandbox (a restricted execution environment)\n\nThe `--mocks` help text was also expanded to better explain the difference between `record` and `off` behavior. Separately, when a plugin's MCP servers can't be enumerated (for example, an invalid manifest, archive, or MCPB bundle), setting `allowRealServers` now runs the real servers instead of refusing or mocking them; without it, an invalid manifest now causes affected cases to be refused outright in record mode, rather than just noted.\n\n**Why**\n\nThese flags make it practical to run plugin evals unattended in automated pipelines and to test against real MCP servers when no mock exists, at the cost of running outside the sandbox's protections.\n\n- Area: Plugin Eval\n- Names: `--trust-plugin`, `--allow-real-servers`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}