Codex CLI 0.123/0.124 regression: WebSocket fallback then stream disconnected before completion on Windows

What version of Codex CLI is running?

codex-cli 0.124.0

What subscription do you have?

Using Codex CLI with ChatGPT Plus / Codex credits.

Which model were you using?

gpt-5.4 with reasoning effort xhigh The same environment was previously stable with Codex CLI 0.122.x. The transport issue started from CLI 0.123.x and persists on 0.124.x.

What platform is your computer?

Microsoft Windows NT 10.0.26200.0

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

Windows Terminal with PowerShell

What issue are you seeing?

Since upgrading Codex CLI from 0.122.x to 0.123.x, and still on 0.124.x, Codex sessions intermittently fail during long-running work.

The CLI first reports that it is falling back from WebSockets to HTTPS transport, then the stream disconnects before completion.

Observed error:

Falling back from WebSockets to HTTPS transport.
stream disconnected before completion: failed to send websocket request: IO error: Connessione interrotta dal software del computer host. (os error 10053)

This happens during active Codex work, often after the session has been running for a while. The same machine/network was stable on CLI 0.122.x. The issue started with 0.123.x and persists on 0.124.x.

The failure interrupts the active task and can leave the session unreliable or unable to complete the response. Opening a new session sometimes helps temporarily, but the issue comes back.

What steps can reproduce the bug?

Uploaded thread: 019dbea5-9921-7112-9c3f-ae0b16f4deea

What is the expected behavior?

Codex CLI should keep the streaming connection stable and complete the task response.

If WebSocket transport fails and the CLI falls back to HTTPS, the fallback should complete reliably without disconnecting before completion. Long-running sessions should not become unreliable after the transport fallback.

Additional information

The issue appears to be a regression introduced in 0.123.x, because 0.122.x was stable on the same Windows machine, terminal, project, and network.

I also submitted feedback from inside the CLI using /feedback before opening this issue.

The error is Windows os error 10053, but the timing strongly correlates with the Codex CLI upgrade from 0.122.x to 0.123.x / 0.124.x.