GitHub issue #49829 in openai/codex, opened 2026-10-01 by xc1427, records a report that opening a Dot-created task in ChatGPT desktop fails with "Failed to resume chat" and "Codex app-server is not available", while the same task opens successfully in ChatGPT web; on a network where direct access to codex-cloud-backend.chatgpt.com times out but an approved proxy works, logs repeatedly show hostKind=durable, failureReason=open_timeout, and WebSocket close code 1006, and installed-code inspection suggests the bundled WebSocket library supplies a custom createConnection without a proxy agent, bypassing Node's environment-aware default agent; the report was filed against ChatGPT desktop 26.928.31416 on macOS with a ChatGPT Pro subscription.
Verbatim Excerpts from Cited Records
“The same task opens successfully in ChatGPT web.”
·
openai/codex (issue 49829 opening body, Environment section)
·
2026-10-01T02:41:41Z
·GitHub Issue ↗
“Logs repeatedly show `hostKind=durable`, `failureReason=open_timeout`, and WebSocket close code `1006`.”
·
openai/codex (issue 49829 opening body, Reproduction section)
·
2026-10-01T02:41:41Z
·GitHub Issue ↗
“Installed-code inspection suggests the bundled WebSocket library supplies a custom `createConnection` without a proxy agent, bypassing Node's environment-aware default agent.”
“This matters in FDE/client environments requiring approved proxy access without additional system-wide traffic interception.”
·
openai/codex (issue 49829 opening body, Expected behavior / possible fixes section)
·
2026-10-01T02:41:41Z
·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 25 comments were read. github-actions[bot] (2026-10-01) flagged potential duplicates #49626, #49522 and #49520; xc1427 (2026-10-01) replied the report pinpoints a proxy bypass in the desktop WebSocket path supported by a standalone reproduction, and asked to keep it open unless that mechanism is confirmed in an existing issue. Independent reproductions and mechanism confirmations across platforms: anye2627 (2026-10-01, Windows 11) reproduced with direct TCP attempts stuck in SYN_SENT and about 15-second open_timeout failures while Chromium and the local app-server used the proxy; lcxhh521 (2026-10-01, macOS) traced the cause to the durable WebSocket using Node ws on a plain Node TLS socket, bypassing Electron's network stack, with a SOCKS agent attached only for hostnames ending in .internal.api.openai.org; kkkzbh (2026-10-04, Fedora Linux) showed an authenticated proxy WebSocket reached HTTP 101 and initialize succeeded while direct access timed out; fj974279207-tech (2026-10-03, macOS), scosmiclia (2026-10-05, macOS, TUN comparison), weijiayua11y (2026-10-05, Windows), masonjian (2026-10-08, macOS), DKalien (2026-10-09, Windows), rdcamelot (2026-10-10, Windows, TCP relay workaround reaching initialized=true), YuanZheng01 (2026-10-10, Windows), dexielitao-svg (2026-10-11, Windows), lurenyi2025 (2026-10-07, macOS), yuc26331-eng (2026-10-12, Windows), jackchen191919-wq (2026-10-14, Windows), nguyen-ammonite (2026-10-14, Windows), wannnngkl (2026-10-29, macOS) and BulgakovMilan (2026-11-14, Windows) add further reproductions and diagnostics, with BulgakovMilan reporting the problem persists after enabling respect_system_proxy and system_proxy_fallback, now with an HTTP 403. No maintainer fix and no retraction appear in the surveyed thread. The claim documents only the original report, not a verified current state.
Falsification probe: If GitHub issue #49829 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn.
Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by
scripts/verify_claim_verbatim.py.