stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)
Resolved 💬 4 comments Opened Feb 19, 2026 by bsheoran-chwy Closed Feb 24, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
NA
What subscription do you have?
chatGPT enterprise
What platform is your computer?
macos
What issue are you seeing?
stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)
What steps can reproduce the bug?
stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)
What is the expected behavior?
stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)
Additional information
stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I’m investigating this behavior as well and wanted to share some structured observations.
This error pattern:
"stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses)"
suggests the client streaming connection (likely SSE or HTTP/2) is being interrupted before the backend completes the response.
Some possible technical causes worth checking:
Questions that may help narrow it down:
If this is a streaming timeout issue, implementing automatic stream reconnection or partial-response recovery might mitigate the user-facing failure.
Happy to help test further if needed.
Thanks for reporting the problem, but there's not enough information for us to investigate further. If you see this again, please use the
/feedbackslash command to upload your logs and session details and include the thread ID in the bug report.This error can be caused by may different things, and without logs it's difficult to say which of those you were experiencing.
Using the vscode plugin I saw this error when using the API key to authenticate, using the login method worked for me.