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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Windows sandbox install provisions a persistent TLS-inspection CA

Use it now
Useful4 Signal0
Sandbox not in their notes

On Windows, /sandbox install now sets up the certificate needed for sandboxed HTTPS, reporting partial success on failure.

/sandbox install
What

/sandbox install on Windows now sets up a certificate authority for sandbox TLS inspection as part of the install, and reports partial success instead of failing outright when that step does not work.

Details
  • Calls ensurePersistentWindowsCa, which generates or reuses a CA under LOCALAPPDATA\sandbox-runtime\ca (ca.json, cert.pem, key.pem) and regenerates it within 30 days of expiry.
  • Trusts the CA for the sandbox account via srt-win user trust-ca.
  • Only runs on Windows and only when the sandbox config source is "managed".
  • Failures return status "partial" with either "The sandbox TLS inspection CA couldn't be trusted for the sandbox user" or "The sandbox TLS inspection CA couldn't be created", and log sandbox_windows_install/trust_ca_failed or persistent_ca_failed.
  • Success messages gain a restart suffix when one is needed.
Evidence

Restart Claude Code to enable TLS inspection for this session.

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