Sweep 22 Sep 2026 · 15:52Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.278 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Reading a new release v2.1.280 First look · 1/6 0 findings $0.00 so far
Claude Code v2.1.235 ·

claude plugin eval rewritten around which plugin is actually loaded

claude plugin eval now checks which plugin is actually loaded before running

TierYou'll noticehow much it should matter to you
Useful3my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaPlugin Evalwhat it touches
KindImprovementsin v2.1.235,
You'll notice

claude plugin eval now checks which plugin is actually loaded before running

The eval command resolves the target, the plugin root, and any untrusted or adopted manifest directory up front, and prints explicit notices when a nearby plugin is not loaded: because it sits above the working directory, falls outside the scope consulted, or its ownership can't be verified. That way a case running without a plugin loaded runs against baseline Claude instead of silently picking up someone's plugin. --eval-dir is now validated and vetted with its own refusal codes, eval_dir_refused and eval_dir_unvettable, the eval directory can be supplied by the plugin manifest, and the empty-result help output now names the directory and manifest it consulted.

Read from
Names in the bundle--eval-dir
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.

Confirmed since Anthropic's documentation has since written up --eval-dir, on Plugins reference. | `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… plugins-reference see the edit
Added since A small documentation edit on Create and distribute a plugin marketplace touched a line naming 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 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
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 plugin eval, on Claude Code changelog.
The name it cites is new in this buildNew in this build: --eval-dir

See this entry in the whole of v2.1.235 →