Claude Code v2.1.251 · 28 Aug 2026
How the evaluation subprocess environment is assembled
The confined-evaluation flag is injected into eval child processes, confirming it's harness plumbing not a setting.
Under the hood
No documentation found Internal Changes
Copy link
Copy markdown
JSON
All of v2.1.251
Under the hood Tier: how much it should matter to you
1 Useful: my rating, 1 to 5
3 Signal: worth watching, 1 to 5
Plugin Eval Area: what it touches
Internal Changes Kind: in v2.1.251, 28 Aug 26
Internal Changes Section of the release
What
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.
Details
Reaches file hard-link checks, artifact read locking, plan-mode denial forcing and subprocess environment construction. No settings file or config lookup reads it.
How sure we are
One source agrees One thing we can check says the same as this entry.
The name it cites is new in this build New in this build: CLAUDE_CODE_EVAL_CONFINED
See this entry in the whole of v2.1.251 →
28 Aug 2026 · 373 entries, this one is #340.
Use it now45 You'll notice200 Nothing to try yet36 Under the hood92
Open the release →
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 339 of 373
Eval sandboxes run with claude.ai MCP servers off
Under the hood Plugin Eval
In v2.1.251 Internal Changes release-page order
Next → · 341 of 373
Eval runs save mock recordings next to their results
Under the hood Plugin Eval