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

[bsheoran-chwy]

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)

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses) #12206
• stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses) #10985
• stream disconnected before completion: error sending request for url (https://chatgpt.com/backend-api/codex/responses) #11741
• Stream disconnected before completion on VPS using ChatGPT OAuth (worked 12 hours prior, reproducible, network verified) #11743
• thread ID 019c4d06-0a03-7ba0-b41d-68f0633d3474 #11453

Powered by Codex Action

[Nadeesha-D-Shalom]

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:

1. HTTP/2 stream reset (RST_STREAM) or idle timeout on macOS network stack
2. Enterprise OAuth token refresh occurring mid-stream
3. Gateway/proxy terminating long-lived streaming connections
4. Backend timeout for long-running responses
5. Network layer TLS renegotiation failure

Questions that may help narrow it down:

• Does this only occur for longer prompts?
• Does it happen after the session has been idle?
• Are there any HTTP status codes logged before disconnect?
• Does disabling VPN/firewall change behavior?
• Is it reproducible on another network?

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.

[etraut-openai]

Thanks for reporting the problem, but there's not enough information for us to investigate further. If you see this again, please use the /feedback slash 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.

[wirthual]

Using the vscode plugin I saw this error when using the API key to authenticate, using the login method worked for me.