{"version":"2.1.269","anchor":"claude-plugin-eval-skips-auto-publishing-its-report-when-t","canonical_anchor":"claude-plugin-eval-skips-auto-publishing-its-report-when-t","heading":"'claude plugin eval' skips auto-publishing its report when the run looks like it was launched by Claude Code itself","tier":"notice","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/claude-plugin-eval-skips-auto-publishing-its-report-when-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### 'claude plugin eval' skips auto-publishing its report when the run looks like it was launched by Claude Code itself\n\n'claude plugin eval' no longer auto-publishes reports when the run looks machine-launched rather than started by a person\n\n**What**\n\nThe `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.\n\n**Why**\n\nThis 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.\n\n- Flag `tengu_quartz_thimble`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.269; this account: on, anonymous baseline: on, compiled default: on)\n- Area: Plugin Eval\n- Names: `--publish-report`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}