The agent proxy detects blocked outbound traffic more reliably using a real WebSocket test.
What's wrong with this entry?
The proxy's egress check now stands up a loopback server, performs an actual WebSocket upgrade and pushes data through it, watching whether the send buffer backs up, which detects outbound traffic being blocked more reliably than a plain connection attempt.
- the handshake gives up after a timeout and reports that instead of hanging
- runs as part of proxy startup and diagnostics
handshake timeout
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.
-
v2.1.239
Agent proxy allowlist narrowed to named Anthropic hosts
Both mention agent proxy
-
v2.1.239
System prompt lists the CLIs already wired up for the agent proxy
Both mention agent proxy
-
v2.1.239
Agent proxy credential placeholders table-driven, PATH search bounded
Both mention agent proxy