Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.221 ·

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

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

Use it now No documentation found New Features
JSON All of v2.1.221
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
SandboxArea: what it touches
New FeaturesKind: in v2.1.221,
What probably matters to youSection of the release
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.

Read from
Names in the bundle/sandbox install

See this entry in the whole of v2.1.221 →

Feedback