Durable host WebSocket ignores proxy

“So the Rust app-server does honor HTTP_PROXY, while the main-process WebSocket does not — inconsistent proxy behavior inside the same app/process tree.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/codex/issues/19951/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Long-lived host WebSocket bypasses system proxy on Windows desktop. The hardcoded wss://codex-cloud-backend.chatgpt.com/ connection ignores HTTP_PROXY and WinINET proxy, dials directly, and dies with open_timeout / 1006.

Is this your bug?

File my report

Where: Windows desktop app
Error text: failureReason=open_timeout
Versions: 0.163.0 to 26.1013.4894.0
Platforms: Windows
How bad: Breaks a normal workflow.

Part of: Cloud WebSocket ignores proxy3 bugs

Dot-created tasks fail to open in desktop behind a proxy6 people
Local PC stays Offline in dot2 people

Not quite your bug?

CLOSE_WAIT socket leak3 people

Original reports2, newest first

Oct 20, 2026Durable host WebSocket (wss://codex-cloud-backend.chatgpt.com/) never establishes and loops on open_timeout / 1006 in the Windows desktop appOn GitHub#55584
Oct 20, 2026bug(windows-os): desktop app "Long-lived" host WebSocket ignores system proxy and HTTP_PROXY, hardcoded URLOn GitHub#55557