{"version":"2.1.304","anchor":"sandbox-proxy-caps-tls-terminated-tunnels-and-times-out-hand","canonical_anchor":"sandbox-proxy-caps-tls-terminated-tunnels-and-times-out-hand","heading":"Sandbox HTTPS interception now caps open connections and times out stalled ones","tier":"notice","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/sandbox-proxy-caps-tls-terminated-tunnels-and-times-out-hand","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Sandbox HTTPS interception now caps open connections and times out stalled ones\n\nWith TLS termination on, the sandbox now allows 256 intercepted connections at once and closes those not set up within 10 seconds\n\n**What**\n\nThe sandbox is the walled-off environment where Claude Code runs commands, with its own proxy controlling network access. When `network.tlsTerminate` is on, that proxy opens up HTTPS connections itself so it can inspect them. It now puts limits on these connections:\n\n- Connections at once: 256 by default. Past that, new connections are refused with \"too many TLS-terminated tunnels at once\". The message points to `network.tlsTerminate.maxTunnels`, the setting that changes the limit.\n\n- Setup timeout: a connection whose secure handshake (the opening exchange that sets up encryption) does not finish in time, 10 seconds by default, is closed.\n\n- Byte budget: a cap on how much data is handled.\n\n- Header size: limits on how large request headers can be.\n\n- Deny header: an optional header used when a request is refused.\n\n**Why**\n\nIf you use TLS termination in the sandbox and a task opens many HTTPS connections at once, some can now be refused or closed. Raise `network.tlsTerminate.maxTunnels` if you hit that limit.\n\n- Area: Sandbox\n- Names: `network.tlsTerminate`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}