Eval report publishing now announces itself, and nested interview runs no longer each publish.
tengu_quartz_thimble Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.233: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.233. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Publishing an eval report now prints Publishing report to claude.ai (private to you) before it happens. Auto-publish is additionally suppressed when the process is an eval interview subprocess, so nested runs do not each publish their own report.
- The parent sets
CLAUDE_CODE_EVAL_INTERVIEW_SESSIONbefore spawning the child; the publish decision checks it on top of the existingtengu_quartz_thimblegate, which defaults to on. - That variable is on the scrub list and is deleted from relaunch environments, so it does not leak into restarted sessions.
Publishing report to claude.ai (private to you)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
claude eval --interactiveis documentedBoth mention eval interview
-
v2.1.234
plugin evalno longer swallows piped inputBoth mention eval
-
v2.1.234
Plugin eval reference documents image grading and new exit codes
Both mention eval