Stream disconnected before completion
Resolved 💬 8 comments Opened Nov 8, 2025 by rajan-openai Closed Dec 23, 2025
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex is running?
codex-cli 0.56.0
What subscription do you have?
ChatGPT Enterprise (signing in with ChatGPT)
Which model were you using?
gpt-5-codex-mini medium
What platform is your computer?
Darwin 24.6.0 arm64 arm
What issue are you seeing?
stream disconnected before completion: An error occurred while processing your request. You can retry your request, or contact us through our help center at
help.openai.com if the error persists. Please include the request ID 9533aa9c-0b12-47f6-bf85-773edc1f24fa in your message.
What steps can reproduce the bug?
It started when I uploaded an image but I am unsure if this was the trigger.
Uploaded thread: 019a63b6-9bb3-7201-ad62-f4c3f9cfb9d8
What is the expected behavior?
The command should have run as desired.
Additional information
" stream disconnected before completion: An error occurred while processing your request. You can retry your request, or contact us through our help center at
8 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Once again? It happens roughly everyday, same time this week...
it just happened to me too. same error in vscode. it says: stream disconnected before completion: An error occurred while processing your request. You can retry your request, or contact us through our help center at help.openai.com if the error persists. Please include the request ID 19298611-0816-4bdd-86b9-1cf8efcbb3dd in your message.
The error stopped coming up for me now but it was strange at the time
If you see this, please use the
/feedbackslash command in the CLI. This will provide us more details that we need to diagnose the issue.This bug report is stale. Closing.
Hi @etraut-openai,
I'm running into this issue intermittently on Azure:
@codeofdusk, this bug report is closed. If you're seeing something similar, please use the
/feedbackslash command to upload your logs and session details and include the thread ID in a new bug report. You might also want to report this to the Azure team so they're aware of the problem.