'claude plugin eval' no longer auto-publishes reports when the run looks machine-launched rather than started by a person
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.
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.
tengu_quartz_thimble On for this account, and not off by defaultThe 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
Added claude plugin eval: run a plugin's eval suite against Claude Code and get scored, reproducible results (JSON + HTML report); see…