Celia Chen 94ebae725e Route exec-server WebSockets through configured proxies (#35056) ...

## Why

Remote environment connections need to honor Codex's effective outbound proxy policy, including when a rendezvous connection reconnects.

## What changed

- Pass the configured `HttpClientFactory` into remote environment transports and use `WebSocketConnector` for exec-server and rendezvous WebSockets.
- Resolve proxy routes asynchronously so these connections can use the configured system proxy.
- Add connector options that preserve Tungstenite's default TLS behavior and enable `TCP_NODELAY` for latency-sensitive rendezvous traffic.

## Testing

- Verify prepared remote environments connect through a configured system proxy.
- Verify initial and reconnected encrypted relay peers use the system proxy.
- Cover default TLS selection and opt-in `TCP_NODELAY` behavior in the WebSocket client.

GitOrigin-RevId: 8a8da2116e37cb3a891269d0c0b037986fecdd3c

2026-07-24 00:16:42 +00:00

..

src

Route exec-server WebSockets through configured proxies (#35056)

2026-07-24 00:16:42 +00:00

BUILD.bazel

websocket-client: add proxy-aware connector (#31622)

2026-07-08 12:57:27 -07:00

Cargo.toml

websocket-client: add proxy-aware connector (#31622)

2026-07-08 12:57:27 -07:00