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.229 Home All releases ←olderv2.1.228 v2.1.231newer→
Claude Code v2.1.229

A failed sandbox startup no longer sticks

You'll notice
Useful4 Signal2
Sandbox

If the sandbox fails to start, a later attempt can now succeed instead of failing forever.

What

When sandbox initialization fails, it now clears its recorded state and returns instead of caching a rejected promise, so a later attempt can succeed. A successful init clears the previous failure reason.

Details
  • The reset covers both whether the sandbox was started with TLS termination and a new flag recording whether the installed network filter actually enforces the allowlist.
  • The settings-change subscription now also re-subscribes to the stream of denied plugin producer directories.
  • A new helper answers whether the sandbox is currently usable without re-running the dependency probe.
Evidence

Sandbox configuration updated from settings change

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.229 →