Follow Discord
Sweep 10 Nov 2026 · 02:18Z Build v2.1.322 539 read Stable v2.1.311 Latest v2.1.322 Next v2.1.322 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.268 ·

Experimental in-process TLS termination and upstream parent-proxy support added to sandbox network config

Sandbox can now terminate HTTPS itself and route traffic through an upstream proxy, both experimental

Nothing to try yet Notable In Development
JSON All of v2.1.268
Nothing to try yetTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
Sandbox NetworkArea: what it touches
In DevelopmentKind: in v2.1.268,
What probably matters to youSection of the release
What

Two new experimental sandbox network settings:

  • network.tlsTerminate lets the sandbox terminate HTTPS connections itself, making request and response bodies visible to request filtering and credential injection; an excludeDomains option opts specific hosts (such as ones using certificate pinning) out of this.
  • network.parentProxy lets the sandbox's proxy route outbound traffic through an upstream HTTP proxy, falling back to the HTTP_PROXY, HTTPS_PROXY, and NO_PROXY environment variables if not explicitly set.

Credential masking now requires tlsTerminate to be turned on, unless you explicitly opt out with allowPlaintextInject (off by default).

Why

Terminating TLS in-process lets the sandbox actually inspect and mask credentials inside encrypted traffic instead of only seeing opaque bytes, but both features are marked experimental, so behavior may still change.

Read from
Names in the bundlenetwork.tlsTerminate
What the documentation says
network.tlsTerminate Configure server-managed settings modified, medium confidence An approval for `sandbox.credentials` or `sandbox.network.tlsTerminate` also covers the [`sandbox.network.allowedDomains`](/docs/en/settings-reference#sandbox-network-alloweddomains) entries in those same delivered settings, because both s… see the edit
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Added since A small documentation edit on Configure the sandboxed Bash tool touched a line naming network.tlsTerminate after this was published. * **TLS termination**: the proxy substitutes the real value inside request contents, so it has to see them. Set [`network.tlsTerminate`](/docs/en/settings-reference#sandbox-network-tlsterminate) so the proxy terminates TLS itself. Without … sandboxing see the edit
Confirmed since Anthropic's documentation has since written up network.tlsTerminate, on All settings. | [`sandbox.network.tlsTerminate`](#sandbox-network-tlsterminate) | Have the [sandbox](/docs/en/sandboxing#network-isolation) proxy terminate TLS so it can read HTTPS requests | Sandbox settings | User or managed | settings-reference see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesnetwork.tlsTerminate on Configure server-managed settings

See this entry in the whole of v2.1.268 →

Feedback