Codex desktop: unstable websocket reconnection after restart when resuming existing sessions
Summary
After quitting/restarting the Codex desktop app and reopening it, continuing an existing/older session often becomes unstable. The task stream repeatedly reconnects and may disconnect before completion, which makes the session unreliable and seriously affects normal use.
Environment
- Product: Codex desktop app
- Version:
26.422.30944 (2080) - Platform: macOS desktop app
Steps to reproduce
- Use a Codex session normally.
- Quit/restart Codex, or close the app and open it again.
- Reopen an existing/old session.
- Start or continue a task in that session.
Actual behavior
The session connection becomes unstable and repeatedly attempts to reconnect. The UI shows reconnect attempts such as:
Reconnecting... 2/5
Reconnecting... 3/5
Reconnecting... 4/5
stream disconnected before completion: websocket closed by server before response.completed
Reconnecting... 5/5
stream disconnected before completion: websocket closed by server before response.completed
After this happens, the session may keep thinking/reconnecting instead of completing the response normally.
Expected behavior
After restarting or reopening Codex, existing sessions should resume normally and the websocket/stream should remain stable until the task completes.
Impact
This happens specifically after restarting/quitting and reopening Codex, then continuing old sessions. It severely interrupts coding workflows because long-running or active sessions become unreliable after reopening the app.
Additional context
I have screenshots showing the repeated reconnect attempts / websocket error and the Codex version dialog. I can provide them if needed.
<img width="2048" height="476" alt="Image" src="https://github.com/user-attachments/assets/a1d9398b-ec58-471a-82ad-c29b76b23538" />
<img width="568" height="382" alt="Image" src="https://github.com/user-attachments/assets/1564ef07-8eef-45f5-9a46-1fd0e0ed4e2a" />
5 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Please use
/feedbackto upload logs and session details, then post the thread ID here.@etraut-openai I submitted
/feedbackfrom the affected resumed Codex desktop session with current session logs included.Thread ID:
019dbc09-f348-7ca0-90b1-c1c9083ed223This feedback was captured from the session affected by the reconnect loop after quitting/restarting Codex and then resuming an existing/old session. The session repeatedly showed reconnect attempts and the error:
I'm getting the same error. Thread ID:
019dc7d7-8f15-7733-84ec-441defa46f85.me too ...
019dd393-8b26-77a3-b9fb-65c8109c1e91