Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.233entry #131

Claude Code v2.1.233 ·

plugin eval --verbose now writes traces to the debug log

Eval --verbose now writes traces to the debug log instead of streaming them live.

Nothing to try yet In Development
JSON All of v2.1.233
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Plugin EvalArea: what it touches
In DevelopmentKind: in v2.1.233,
In DevelopmentSection of the release

Verbose trace logging for the early-access plugin eval command, readable via --debug-file.

What

--verbose on the plugin eval subcommand no longer streams the trace as it runs; it logs per-message trace events to the debug log and points at --debug-file for reading them. The plugin eval command is in early access.

Usage
claude plugin eval --verbose --debug-file trace.log
Evidence

Log per-message trace events to the debug log (use --debug-file to read them)

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle--verbose--debug-fileplugin eval
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 --verbose, on Plugins reference. This table lists the options most runs use. Run `claude plugin eval --help` for the complete set, including `--case`, `--tag`, `--output-dir`, `--report`, `--allow-real-servers`, `--keep-temp`, and `--verbose`. 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
Confirmed since Anthropic's documentation has since written up --debug-file, on Hooks reference. Hook execution details are written to the debug log file. Start Claude Code with `claude --debug-file <path>` to write the log to a known location, or run `claude --debug` and read the log at `~/.claude/debug/<session-id>.txt`. The `--debu… hooks see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --debug-file, on Hooks reference.

See this entry in the whole of v2.1.233 →

Feedback