Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.269 ·

New CLI flags for the plugin-eval command: --trust-plugin and --allow-real-servers

claude plugin eval adds --trust-plugin for CI and --allow-real-servers to run real MCP servers without mocks

Use it now Notable New Features
JSON All of v2.1.269
Use it nowTier: how much it should matter to you
5Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Plugin EvalArea: what it touches
New FeaturesKind: in v2.1.269,
What probably matters to youSection of the release
What

The plugin evaluation command gains two new flags:

  • --trust-plugin: skips the first-run trust prompt, meant for use in CI (continuous integration) pipelines, similar in spirit to --dangerously-skip-permissions
  • --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)

The --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.

Why

These 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.

Read from
What the documentation says
Since it was published

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 Test plugins with evals touched a line naming --trust-plugin after this was published. The first time you run `claude plugin eval` against a directory, Claude Code asks `Trust this plugin directory?` before it loads anything from it, unless you already accepted the trust prompt there in an interactive `claude` session. Insid… plugin-evals see the edit
Confirmed since Anthropic's documentation has since written up --trust-plugin, on Test plugins with evals. | `--trust-plugin` | Off | Skip the first-run trust prompt for a plugin whose code and suite you'd run yourself. Pass it in CI so the job is never refused by or left waiting at the prompt. See [What a run can access](#security) | plugin-evals see the edit
Confirmed since Anthropic's documentation has since written up --allow-real-servers, on Test plugins with evals. When a case asked for a tool you didn't grant, the progress output lists it as `not granted`. Tools on a [mocked](#mock-mcp-servers) MCP server need no grant. Tools on a real plugin MCP server need both the server started, with `--allow-re… plugin-evals see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --allow-real-servers, on Test plugins with evals.
Anthropic's release notes agreeAdded claude plugin eval: run a plugin's eval suite against Claude Code and get scored, reproducible results (JSON + HTML report); see…
The name it cites is new in this buildNew in this build: --allow-real-servers

See this entry in the whole of v2.1.269 →

Feedback