Transport timeouts

[albertodimas]

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

1. Priority investigation for Pro subscribers experiencing this issue
2. Timeline for fix
3. Credit/compensation for service unavailability

---

Related issues: #3478, #3835, #7198, #8256

[github-actions]

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

• Constantly reconnecting #8362

Powered by Codex Action

[albertodimas]

Not closing as duplicate.

While the symptoms are similar to #8362, this issue specifically documents:

1. Impact on Pro subscribers ($200/month tier)
2. Service unavailability duration (Dec 11-20, 9+ days)
3. Request for acknowledgment and compensation for paying customers

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]

If you see this again, please use the /feedback command to upload your logs and session, and post the thread ID here.

[albertodimas]

Thanks for the response. I'll use /feedback next time it occurs and post the thread ID here.

[kronholmeliah]

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]

@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]

Closing - the transport timeout issues have been resolved. The CLI is working properly again. Thanks to the OpenAI team for addressing this.

[TheSacud]

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]

Plus user experiencing same issue and it seems to degrade.

019b4a6b-a231-7353-8a2b-3285530a8663

[georgeconst]

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