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.196 Home All releases ←olderv2.1.195 v2.1.197newer→
Claude Code v2.1.196

Mux Proxy (Combined HTTP+SOCKS Proxy)

The internal proxy infrastructure has been replaced with a single multiplexed proxy that handles both HTTP and SOCKS4/5 on one port. Previously, separate HTTP and SOCKS proxies listened on separate ports; now a single mux proxy inspects the first byte and routes accordingly.

Details
  • On Linux/macOS, the HTTP backend uses a Unix domain socket under srt-mux-<pid>-<seq>.sock.
  • On Windows, the HTTP backend falls back to a loopback TCP port.
  • The SOCKS handler receives the raw connection directly when the first byte is 0x04 (SOCKS4) or 0x05 (SOCKS5).
  • A first-byte timeout destroys idle connections that never send data.
Evidence

New mux proxy (search for "Mux proxy (HTTP+SOCKS) listening on localhost:")

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.196 →