Windows: responses_websocket connect to chatgpt.com/backend-api/codex/responses times out while responses_http succeeds

Resolved 💬 5 comments Opened Mar 31, 2026 by edswangren Closed Mar 31, 2026

What version of Codex CLI is running?

0.117.0

What subscription do you have?

Enterprise

Which model were you using?

gpt-5.4

What platform is your computer?

Windows 11 x86_64

What terminal emulator and version are you using (if applicable)?

Windows Terminal

What issue are you seeing?

Codex intermittently selects responses_websocket, then stalls for ~15s per attempt and retries repeatedly before falling back to a working HTTP path.

From ~/.codex/log/codex-tui.log:

codex_api::endpoint::responses_websocket: connecting to websocket: wss://chatgpt.com/backend-api/codex/responses
event.name="codex.websocket_connect" duration_ms=15015 success="false" error.message="timeout"

Immediately after websocket failures, the same session can succeed with:

transport="responses_http"
POST https://chatgpt.com/backend-api/codex/responses

What steps can reproduce the bug?

  1. Start a fresh Codex CLI session on Windows using ChatGPT auth.
  2. Send a prompt.
  3. On affected runs, Codex uses responses_websocket and retries after repeated ~15s connect timeouts. The UI will read "Retrying (N/5)..." until the 5 attempts are exhausted, then switches to HTTP, which works.

What is the expected behavior?

websocket requests don't so often timeout for no apparent reason.

Additional information

Relevant log (RUST_LOG=trace) fields on failing websocket attempts:

transport="responses_websocket"
websocket.warmup=false
endpoint="/responses"
auth_mode="Chatgpt"
auth.header_attached=true
auth.retry_after_unauthorized=false
auth_error=""
auth_error_code=""

View original on GitHub ↗

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