A confined evaluation mode exists that Claude Code only sets on its own eval subprocesses.
What's wrong with this entry?
A new environment variable, CLAUDE_CODE_EVAL_CONFINED, appears 26 times in this build and not at all in the previous one. Claude Code sets it to 1 on subprocesses it spawns for evaluation runs rather than reading it from your settings, so every branch it controls is inert in an ordinary session.
- Gates git-source teleport refusals, hard-link checks on files, forced permission denials, and network fetch confinement.
- Added to the three lists of environment variables preserved when spawning privileged worker and background subprocesses.
- Set alongside
CLAUDE_CODE_EVAL_ARTIFACT_STUB_DIRon the same spawn.
CLAUDE_CODE_EVAL_CONFINED, v.CLAUDE_CODE_EVAL_CONFINED = "1"
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.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
-
v2.1.234
claude plugin evalhandles termination signals and cleans up its outputBoth mention eval