Windows: WebSocket transport times out with respect_system_proxy, works with HTTP_PROXY/HTTPS_PROXY

Open 💬 4 comments Opened Jun 25, 2026 by fei1025

What version of the Codex App are you using (From “About Codex” dialog)?

0.142.1

What subscription do you have?

plus

What platform is your computer?

Windows 10

What issue are you seeing?

With network_proxy and respect_system_proxy enabled on Windows, Codex can use the system proxy for HTTPS requests, but WebSocket transport times out and falls back to HTTPS:

Falling back from WebSockets to HTTPS transport. request timed out

If I set HTTP_PROXY and HTTPS_PROXY to the same proxy, WebSocket transport works correctly. It seems WebSocket transport does not fully respect the Windows system proxy configuration.

What steps can reproduce the bug?

Behavior:

  • HTTPS requests work through Windows system proxy.
  • WebSocket transport times out and falls back to HTTPS.

When HTTP_PROXY/HTTPS_PROXY are set to the same proxy:

  • WebSocket transport works correctly.

It appears that WebSocket transport does not fully honor the Windows system proxy resolver.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗