Responses WebSocket closes before response.completed

[evilfps]

Summary

Codex intermittently loses the Responses WebSocket stream before receiving response.completed, causing turns to retry or fail with:

stream disconnected before completion: websocket closed by server before response.completed

Reference/session id from the affected Codex run:

019de6d6-2863-7401-99e4-af3ed9b0f4a9

Environment

• Codex CLI: codex-cli 0.128.0
• OS: macOS 26.4.1, Darwin 25.4.0, arm64
• Model: gpt-5.5
• Wire API: responses
• Transport: responses_websocket
• Provider: OpenAI

What is happening

During normal Codex turns, the runtime opens a Responses WebSocket connection, then the connection closes before the stream emits a final response.completed event. The client retries the sampling request, but this has been recurring across turns.

Representative local log lines:

model_client.stream_responses_websocket{model=gpt-5.5 wire_api=responses transport="responses_websocket" api.path="responses" turn.has_metadata_header=true websocket.warmup=false}: codex_core::client: new
model_client.websocket_connection{provider=OpenAI wire_api=responses transport="responses_websocket" api.path="responses" turn.has_metadata_header=true}: codex_core::client: new
model_client.websocket_connection{provider=OpenAI wire_api=responses transport="responses_websocket" api.path="responses" turn.has_metadata_header=true}: codex_core::client: close
codex_core::session::turn: stream disconnected - retrying sampling request (1/5 in 206ms)...

The stream appears to close at the transport layer rather than because of project code. The active project has no OpenAI/WebSocket streaming implementation; this is coming from Codex runtime logs.

Network sanity check

I checked local connectivity outside the Codex sandbox:

dscacheutil -q host -a name api.openai.com
name: api.openai.com
ip_address: 172.66.0.243
ip_address: 162.159.140.245

nc -vz api.openai.com 443
Connection to api.openai.com port 443 [tcp/https] succeeded!

Inside the sandbox, DNS/connectivity probes can fail, but the host network itself can resolve and connect to api.openai.com:443.

Expected behavior

Codex should keep the Responses WebSocket stream open until it receives response.completed, or surface a more specific upstream/server-close reason when the server closes the socket before completion.

Actual behavior

The WebSocket closes before response.completed, producing repeated stream disconnected retries and occasionally interrupting completion of the turn.

Notes

This looks upstream/runtime-side rather than repository/app-side:

• The affected project is a small Vite app with no OpenAI streaming code.
• The failure happens in Codex's responses_websocket transport path.
• Host-level DNS and TCP connectivity to api.openai.com:443 succeed.

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Codex desktop: unstable websocket reconnection after restart when resuming existing sessions #19703
• Codex CLI 0.123/0.124 regression: WebSocket fallback then stream disconnected before completion on Windows #19330
• stream disconnected before completion reproduces after recreating the conversation #19983
• Responses streams need lifecycle diagnostics for close, timeout, and partial-output failures #19745

Powered by Codex Action