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

Claude Code v2.1.299 ·

Sandbox network proxy now checks responses before passing them on

The sandbox network proxy now checks each response's status and headers before forwarding it, rather than passing it straight through

You'll notice Improvements
JSON All of v2.1.299
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SandboxArea: what it touches
ImprovementsKind: in v2.1.299,
ImprovementsSection of the release

Unclear What the new check rejects, and so which responses are now blocked, is not known.

What

The sandbox is a restricted environment Claude Code can run commands in, and its network proxy is the go-between that handles their web traffic. When a response comes back from the outside server, the proxy used to forward its status and headers to the command and stream the rest straight through. It now runs the status and headers through a check first and forwards the response only if that check passes. This applies both to the normal proxy path and to the path that decrypts secure (TLS) traffic for inspection.

Errors from the outside server are still logged as before.

Why

This looks like a tightening of how the sandbox proxy handles responses, which matters if you rely on the sandbox to filter network access. Some responses that used to get through may now be stopped.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat the new check rejects, and so which responses are now blocked, is not known.

See this entry in the whole of v2.1.299 →

Feedback