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 ·

'claude plugin eval' skips auto-publishing its report when the run looks like it was launched by Claude Code itself

'claude plugin eval' no longer auto-publishes reports when the run looks machine-launched rather than started by a person

You'll notice Notable Improvements
JSON All of v2.1.269
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Plugin EvalArea: what it touches
ImprovementsKind: in v2.1.269,
What probably matters to youSection of the release
What

The claude plugin eval command normally publishes its report automatically. Now, if the run looks like it was started by another Claude Code session rather than a person directly (detected via the CLAUDE_CODE_CHILD_SESSION environment variable, or CLAUDECODE combined with no interactive terminal), the report is kept local by default instead. The CLI prints a note that --publish-report must be passed explicitly to publish it in that case.

Why

This stops eval reports from being auto-published when Claude Code itself is the one running the eval (for example, as part of an automated or nested workflow), keeping publication reserved for runs a person actually initiated.

Read from
Names in the bundle--publish-report
Feature flag
tengu_quartz_thimble On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.1.269: on

Read once, for one account on one subscription tier, against v2.1.269. It isn't a statement about your account. What a flag value here can and cannot tell you

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 --publish-report, on Test plugins with evals. | `--publish-report` | | Publish the report even where it would stay local by default, such as a run a Claude Code session started | 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 --publish-report, 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…

See this entry in the whole of v2.1.269 →

Feedback