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

/sandbox install provisions and trusts the managed TLS CA on Windows

Use it now
Useful4 Signal0
Sandbox not in their notes

On Windows, sandboxed HTTPS now works after /sandbox install without a manual certificate trust step.

/sandbox install
What

The Windows install path now creates and trusts the managed sandbox TLS inspection CA, so sandboxed HTTPS works without a manual trust step.

Details
  • The install path became async and runs a CA trust step when the CA source is "managed".
  • Failures are reported as partial installs: "The sandbox TLS inspection CA couldn't be trusted for the sandbox user: " or "The sandbox TLS inspection CA couldn't be created: ", both ending "Sandboxed HTTPS won't work — run /sandbox install again to retry.".
  • Failures are recorded as "trust_ca_failed" and "persistent_ca_failed" under "sandbox_windows_install".
  • A UAC-cancelled install on an already-provisioned user can now still succeed, and the result message may gain " Restart Claude Code to enable TLS inspection for this session."
  • Windows only, and the trust step only runs for a managed CA source.
Evidence

sandbox_windows_install

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 →