stream disconnected before completion: stream closed before response.completed (regression in 26.825.51511)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Description
Since version 26.825.51511 (released 2026-08-30), every response ends with a reconnect error:
stream disconnected before completion: stream closed before response.completed
The issue did not occur on the previous version. Timing matches the regression reported in #41799.
Environment
- App version: 26.825.51511 (released 2026-08-30)
- OS: Windows 11
- wire_api:
esponses\ - Custom provider: third-party OpenAI-compatible endpoint
Config (redacted)
\\ oml
[model_providers.custom]
base_url = 'https:///v1'
wire_api = 'responses'
supports_websockets = false
\\
Steps to reproduce
- Configure a custom provider with \wire_api = 'responses'\
- Send any message
- After response generation, Codex shows reconnecting error and the message above
Expected behavior
Response completes normally without reconnect errors.
Additional notes
The upstream provider sends a valid SSE stream and closes the connection normally, but Codex does not receive the
esponse.completed\ event before the stream closes, triggering the reconnect loop. This behavior started with 26.825.51511 and did not occur on the prior version.
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
Start by reproducing the issue with a custom provider using wire_api = 'responses' and supports_websockets = false, then trace the response stream and reconnect handling. Compare behavior with the previous version and verify that a valid SSE stream closing after response generation completes without a reconnect error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100