Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.251 Home All releases ←olderv2.1.250
Claude Code v2.1.251

Kept eval sandboxes can be sealed after a run

Under the hood
Useful1 Signal3
Plugin Eval

Kept eval sandboxes can be sealed unreadable after a run, with ownership and path checks.

What

The internal eval harness can now seal a sandbox directory it keeps after a run, setting it unreadable and verifying ownership, inode and that it is not the home or temp directory, with explicit failure messages on Windows and when running as root. It also indexes staging directories for stub artifacts produced during a run.

Details
  • Harness code only, not reachable from a normal session.
Evidence

eval kept-sandbox seal did not take

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.

See this entry in the whole of v2.1.251 →