Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.269 ·

claude plugin eval gains a --concurrency flag

claude plugin eval gains a --concurrency flag to run up to 8 test cases at once

TierUse it nowhow much it should matter to you
Useful5my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaPlugin Evalwhat it touches
KindNew Featuresin v2.1.269,
Use it now Notable

claude plugin eval gains a --concurrency flag to run up to 8 test cases at once

What

The claude plugin eval command (which runs a plugin's test suite and produces a scored report) now supports a -j, --concurrency <n> option. It accepts a whole number from 1 to 8 (default 1) and controls how many agent runs execute at the same time. All of these runs share your account's rate limit, progress lines may interleave in the output, but results and the final report still keep the original case order.

The JSON report also now includes a concurrency field recording the value used for that run.

Why

This lets larger eval suites finish faster by running multiple cases in parallel instead of one at a time, while keeping results easy to read in their original order.

Read from
Names in the bundle--concurrency
What the documentation says
claude plugin eval Claude Code changelog modified, high confidence * 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` see the edit
claude plugin eval Error reference modified, high confidence You ran [`claude plugin eval`](/docs/en/plugin-evals) or `claude plugin eval init` and it exited 1 with one of these messages before doing anything: see the edit
claude plugin eval Plugins reference modified, high confidence | `experimental.evals` | string\|array | Directory below the plugin root that holds the plugin's [eval cases](/docs/en/plugin-evals#use-a-different-eval-directory), when it isn't the default `evals/`. `claude plugin eval --eval-dir` overri… see the edit
--concurrency Plugins reference modified, high confidence | `-j, --concurrency <n>` | Agent sessions to run at once, 1 to 8. They share your rate limit | `1` | see the edit
claude plugin eval Test plugins with evals modified, high confidence You don't have to write the suite manually. `claude plugin eval init` asks you about your plugin, proposes the cases and graders, tries them, and writes the files. You can also ask Claude to do the same from a session you already have open. see the edit
claude plugin eval Create and distribute a plugin marketplace modified, medium confidence 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 … see the edit
claude plugin eval Create plugins modified, medium confidence Trying the plugin with `--plugin-dir` tells you it can work. To find out how often Claude actually reaches for it and gets the right result, run it against a set of test prompts with [`claude plugin eval`](/docs/en/plugin-evals). Each prom… see the edit
claude plugin eval Extend Claude with skills modified, medium confidence Two tools automate that comparison. For a skill that ships in a [plugin](/docs/en/plugins), [`claude plugin eval`](/docs/en/plugin-evals) runs each prompt in an isolated session with and without the plugin, scores it with graders you defin… see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesclaude plugin eval on Claude Code changelog
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: --concurrency

See this entry in the whole of v2.1.269 →