Codex Desktop 26.623.101652: stream disconnected before completion during long-running task

What version of the Codex App are you using (From “About Codex” dialog)?

Codex Desktop 26.623.101652

Released Jul 3, 2026

What subscription do you have?

ChatGPT Pro

What issue are you seeing?

A long-running Codex Desktop task disconnected and became blocked before completion.

Observed error:

stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)

The session first showed reconnect attempts (Reconnecting 3/5, then Reconnecting 5/5) and then failed with the error above. The task had been running for about 1h 34m before the disconnect. The UI then showed the goal as blocked, so the task could not continue normally.

I also submitted in-app feedback with current Codex session logs included.

Feedback ID:

019f19a4-c0d8-7a63-adf0-8bc6b6f61863

What steps can reproduce the bug?

1. Open Codex Desktop on macOS.
2. Start a long-running goal/task in Full Access mode.
3. Let the task continue for an extended period. In this case it was doing VM/VNC-related work and had been running for about 1h 34m.
4. Observe the reconnect loop.
5. After the final reconnect attempt, Codex fails with:

stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)

What is the expected behavior?

Codex should either recover the stream and continue the running task, or fail gracefully in a way that preserves task state and allows the user to resume/retry without losing the long-running session progress.

What is the actual behavior?

The task disconnects after repeated reconnect attempts, reports stream disconnected before completion, and leaves the goal blocked.

Additional information

Environment from screenshots:

• App: Codex Desktop 26.623.101652
• OS: macOS Tahoe 26.5.2
• Device: MacBook Pro 16-inch, Apple M5 Max, 128 GB memory
• Model setting visible in the session: 5.5 Extra High
• In-app feedback was uploaded with logs included: 019f19a4-c0d8-7a63-adf0-8bc6b6f61863

Potentially related existing reports include #30958, #29794, and #30777, but this report includes a newer app build and an in-app feedback ID with logs.