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.
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.233: on
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
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
New in this build: CLAUDE_CODE_EVAL_INTERVIEW_SESSION