codex - 💡(How to fix) Fix `stream disconnected before completion` reproduces after recreating the conversation [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19983Fetched 2026-04-29 06:24:13
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

A conversation that was recreated from scratch still hits the same failure mode during generation. The model starts responding normally, then the stream disconnects before completion and the desktop client retries 5 times.

Error Message

  • The response begins normally and then stops mid-stream.
  • The client shows:
    • Reconnecting... 1/5
    • Reconnecting... 2/5
    • Reconnecting... 3/5
    • Reconnecting... 4/5
    • Reconnecting... 5/5
    • stream disconnected before completion: An error occurred while processing your request.
  • The issue reproduces even after recreating the conversation.

Root Cause

Related Issues

This appears to be related to:

  • #19440 - Codex App reconnect loop and stream disconnected before completion
  • #19690 - Codex Desktop gets stuck reconnecting because failed/completed turns are restored with markedStreaming=true
  • #18960 - Frequent reconnect loop in Codex App: websocket closed by server before response.completed
RAW_BUFFERClick to expand / collapse

stream disconnected before completion reproduces after recreating the conversation

Summary

A conversation that was recreated from scratch still hits the same failure mode during generation. The model starts responding normally, then the stream disconnects before completion and the desktop client retries 5 times.

Steps to reproduce

  1. Start a new conversation in the Codex desktop app.
  2. Run the same image-generation workflow prompt again in a fresh chat.
  3. Let the model begin streaming its response.
  4. Observe that the stream disconnects before completion and the client shows repeated reconnect attempts.

Observed behavior

  • The response begins normally and then stops mid-stream.
  • The client shows:
    • Reconnecting... 1/5
    • Reconnecting... 2/5
    • Reconnecting... 3/5
    • Reconnecting... 4/5
    • Reconnecting... 5/5
    • stream disconnected before completion: An error occurred while processing your request.
  • The issue reproduces even after recreating the conversation.

Request IDs

  • 3c818545-aead-41f8-a4fe-a75128ed737c
  • 8b909f78-0b3c-4d37-96b5-322bbd83d373

Local log signals

  • Received turn/started for unknown conversation
  • Timed out waiting for structured result

Notes

  • I do not see a direct 5xx or socket error in the local logs, but the repeated reconnects and unknown-conversation events suggest a conversation routing or stream stability problem.
  • I can share the relevant local log excerpts if helpful.

Environment

  • Codex Desktop Version: [请填写版本号,如 26.422.30944]
  • macOS Version: [如 macOS 15.x]
  • Model: gpt-5.3-codex

Related Issues

This appears to be related to:

  • #19440 - Codex App reconnect loop and stream disconnected before completion
  • #19690 - Codex Desktop gets stuck reconnecting because failed/completed turns are restored with markedStreaming=true
  • #18960 - Frequent reconnect loop in Codex App: websocket closed by server before response.completed

extent analysis

TL;DR

Investigate conversation routing and stream stability issues, potentially related to the gpt-5.3-codex model and Codex Desktop App version.

Guidance

  • Review local log excerpts for patterns or errors related to conversation routing and stream stability, such as Received turn/started for unknown conversation and Timed out waiting for structured result.
  • Compare the behavior with related issues (#19440, #19690, #18960) to identify potential common causes or workarounds.
  • Verify if the issue persists with different models or Codex Desktop App versions to isolate the problem.
  • Check for any updates or fixes related to conversation routing and stream stability in the Codex Desktop App or gpt-5.3-codex model.

Notes

The issue may be specific to the gpt-5.3-codex model or Codex Desktop App version, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Investigate and potentially update the Codex Desktop App or gpt-5.3-codex model to a version that addresses conversation routing and stream stability issues, as suggested by related issues.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix `stream disconnected before completion` reproduces after recreating the conversation [1 comments, 2 participants]