The confined-evaluation flag is injected into eval child processes, confirming it's harness plumbing not a setting.
What's wrong with this entry?
The confined-evaluation variable is written directly into a spawned child's environment, next to the artifact stub directory and an internal feature-flag override variable, confirming it is harness plumbing rather than a configuration key.
- Reaches file hard-link checks, artifact read locking, plan-mode denial forcing and subprocess environment construction.
- No settings file or config lookup reads it.
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