Richer eval failure reporting sits behind the plugin eval early-access gate.
What
Eval run summaries now separate ok, error and exit outcomes. A non-zero exit produces an error built from the result message, or from the exit code plus the tail of stderr, falling back to "(no stderr)" when there is none. Behind the plugin eval early-access gate.
Details
- Runs where a top-level assistant message reported
authentication_failedoroauth_org_not_allowedare now flagged as auth-rejected rather than as generic errors.
Evidence
(no stderr)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundleclaude plugin eval
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 Create and distribute a plugin marketplace touched a line naming claude plugin eval after this was published.
Test your marketplace before sharing. Validation checks file structure; to test whether a plugin changes what Claude does on realistic prompts, run its eval suite with [`claude plugin eval`](/docs/en/plugin-evals) before you publish a new …plugin-marketplaces see the edit
Confirmed since
Anthropic's documentation has since written up claude plugin eval, on Claude Code changelog.
* Added `claude plugin eval`: run a plugin's eval suite against Claude Code and get scored, reproducible results (JSON + HTML report); see `claude plugin eval --help`changelog 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 claude plugin eval, on Claude Code changelog.