Repository navigation
Transport timeouts #8371
Description
Environment
- Codex CLI version: 0.76.0
- Subscription: Pro ($200/month)
- OS: Linux (Ubuntu)
- Issue start date: December 11, 2025
Problem
Constant "stream disconnected before completion: Transport error: timeout" errors making Codex CLI unusable.
The error occurs consistently after working for a short period, regardless of task complexity. This has been happening continuously since December 11, 2025.
What I've tried
- Updated to latest version (0.76.0)
- Creating new sessions instead of using resume
- Shorter prompts/tasks
- No VPN or proxy active
- Verified network connectivity is stable
Expected behavior
As a Pro subscriber paying $200/month, I expect the CLI to function reliably without constant timeout disconnections.
Actual behavior
⚠️ stream error: stream disconnected before completion: Transport error: timeout
retrying 1/5 in 201ms…
This repeats until all retries are exhausted, then fails completely.
Impact
- Unable to use the service I'm paying for since December 11 (9+ days)
- Productivity severely impacted
- Considering requesting partial refund for service unavailability
Request
- Priority investigation for Pro subscribers experiencing this issue
- Timeline for fix
- Credit/compensation for service unavailability
Activity
github-actions commentedon Dec 20, 2025
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
albertodimas commentedon Dec 21, 2025
Not closing as duplicate.
While the symptoms are similar to #8362, this issue specifically documents:
The #8362 issue doesn't address the business impact on paying Pro users.
This should remain open for visibility on how this affects premium subscribers.
etraut-openai commentedon Dec 21, 2025
If you see this again, please use the
/feedbackcommand to upload your logs and session, and post the thread ID here.albertodimas commentedon Dec 21, 2025
Thanks for the response. I'll use
/feedbacknext time it occurs and post the thread ID here.kronholmeliah commentedon Dec 21, 2025
I'm only a plus user but have been experiencing the same problems as @albertodimas for a couple of days now.
I just captured the issue using /feedback
Thread ID: 019b412f-6f91-7293-a6be-1c4a8ee262ff
etraut-openai commentedon Dec 21, 2025
@kronholmeliah, the error you're seeing ("error decoding response body") is not the same as @albertodimas ("Transport error: timeout"). We are tracking the "error decoding response body" issue in #8302.
albertodimas commentedon Dec 21, 2025
Closing - the transport timeout issues have been resolved. The CLI is working properly again. Thanks to the OpenAI team for addressing this.
TheSacud commentedon Dec 22, 2025
I'm also plus user but have been experiencing the same problems as @albertodimas for a couple of days now.
v0.77.0
Thread ID 019b4549-0c5f-73f3-b274-79a027bca180
alanfloch commentedon Dec 23, 2025
Plus user experiencing same issue and it seems to degrade.
019b4a6b-a231-7353-8a2b-3285530a8663
georgeconst commentedon Dec 23, 2025
Plus user, experiencing the same issue for the last week, only now it got worse, making Codex mostly unusable.
Thread ID: 019b4bd9-c446-74d1-bb79-1cb915e2dcf2
4 remaining items
pdfquesada commentedon Dec 26, 2025
I’m a Plus user and I’m having the exact same problem.
It doesn’t matter which model I switch to (5.1-Codex-Max, 5.2-Codex, or whatever). The issue is always the same: it starts thinking, then I get “Reconnecting 1/5…”, and eventually it ends with:
“stream disconnected before completion: Transport error: timeout”
ID: 019b5a6b-1d03-7e93-8a0a-3e53ffb14c9f
etraut-openai commentedon Dec 26, 2025
@pdfquesada, are you sure that you have seen this with the 5.1 series models? The logs that you uploaded (thank you!) show that you're using 5.2-Codex. The reason I ask is that we haven't seen any reports of this from 5.1 series models.
K4leri commentedon Dec 31, 2025
same for me thread ID 019b75e7-1c78-7b71-8136-2a73d660c354
SudoPlz commentedon Jan 8, 2026
same issue ID:
019b99ec-3a8a-7c23-a734-70fe57ff590blzcmian commentedon Jan 8, 2026
same problem:019b9c33-cd61-71f0-8ac9-be9367dcd8e6
lzcmian commentedon Jan 8, 2026
on gpt 5.1: 019b9c8a-0ecf-7592-a539-ba763e8f6cc3
tzimmer63 commentedon Jan 8, 2026
same here: 019b9cea-0aa0-73b0-b8a3-97de083d1d70
spariev commentedon Jan 12, 2026
same here - 019bb1a7-08f1-7463-a35d-50f1f65252b1
Radar-Lei commentedon Jan 12, 2026
same here: 019bb464-68ff-7b23-802b-a8bcd22826d8
reconnecting constantly with all models, including 5.2 and 5.1
fmhall commentedon Jan 12, 2026
Same here, but only with xhigh thinking on the beefier models
etraut-openai commentedon Jan 13, 2026
We think we have mitigated this issue. There are times when the "beefier models" (to quote @fmhall) take longer to generate the next batch of tokens during streaming, and this can sometimes exceed an HTTP timeout value.
I'm going to mark this bug as closed, but if you see this again in the next few days, please use
/feedbackto upload your logs and post your thread ID here.mattiasflodin commentedon Jan 22, 2026
Still happening with 0.87 (thread ID: 019be7b5-f905-78d2-8589-9d9edd1a9ebc); not sure which version this was supposed to be mitigated in. In addition to your measures to reduce the likelihood of this issue, I think it would be helpful if the CLI had some more graceful way of dealing with it when it does happen. Right now I'm kind of stuck and basically need to start a new chat after the failure, since I can't re-trigger the call to the backend - at least not without sending additional dummy messages.