[Windows] Codex Desktop repeatedly reconnects and fails with "stream disconnected before completion", while CLI works normally
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.5k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.803.81509
What subscription do you have?
ChatGPT Pro
What platform is your computer?
Windows 11 x64
What issue are you seeing?
Starting today (2026-08-11), Codex Desktop on Windows has become unstable.
During normal tasks, Codex Desktop repeatedly shows:
Reconnecting... 1/5
Reconnecting... 2/5
Reconnecting... 3/5
...
Reconnecting... 5/5
and eventually fails with:
stream disconnected before completion: An error occurred while processing your request. You can retry your request, or contact us through our help center at help.openai.com if the error persists.
Request ID:
223e0bca-e8c2-4d81-a0a7-52e45aa9b88b
Important observation:
Codex CLI on the SAME Windows machine, SAME network, and SAME OpenAI account is still working normally.
The issue appears to affect Codex Desktop specifically.
In some cases, local commands complete successfully, but the Desktop response stream disconnects before the turn completes.
This problem started today and happens repeatedly.
What steps can reproduce the bug?
-
Open Codex Desktop on Windows.
-
Open an existing thread or create a new thread.
-
Send a normal coding request.
-
Codex begins processing normally.
-
After some time, the Desktop app starts showing repeated reconnect attempts:
Reconnecting... 1/5
Reconnecting... 2/5
Reconnecting... 3/5
... -
The request eventually fails with:
stream disconnected before completion: An error occurred while processing your request.
-
Retry the same request or start another task. The issue happens repeatedly.
Important comparison:
Codex CLI works normally on the SAME computer, SAME network, and SAME OpenAI account while Codex Desktop repeatedly disconnects.
Request ID:
223e0bca-e8c2-4d81-a0a7-52e45aa9b88b
The issue started on 2026-08-11.
What is the expected behavior?
Codex Desktop should maintain a stable response stream and complete the task normally without repeatedly entering reconnect loops.
If a transient network interruption occurs, the Desktop app should recover and resume the response instead of terminating the turn with "stream disconnected before completion".
Since Codex CLI works normally on the same machine, network, and account, Codex Desktop should behave consistently with the CLI.
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are identified in the issue. Start by reproducing the reconnect loop in Codex Desktop on Windows and compare its response-stream behavior with the working CLI under the same conditions, using request ID 223e0bca-e8c2-4d81-a0a7-52e45aa9b88b. Done means Desktop completes normal tasks without repeated reconnects or premature stream-disconnection failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100