Codex stream disconnected before completion
Reports where streamed responses disconnect, fail mid-task, or show transport/backend response errors.
Neutral experience collection
Report Codex stream errors
We are collecting concrete reports from Codex CLI, TUI, VS Code, and related tool users who have seen “stream disconnected before completion” errors, retry loops, degraded sessions, long-running failures, or usage costs that appeared to grow without usable output.
Stream disconnects
Retry loops
20-50+ minute requests
Unexpected usage
Codex Errors to Document
Reports are most useful when they include the exact Codex error text people search for, timing, tool version, model, and whether restarting the session changed the outcome.
Codex retrying or reconnecting loops
Repeated retries after a stream failure, including sequences of 5-30+ attempts or repeated reconnect messages.
Codex usage credits after failed output
Cases where limits, credits, or usage totals appear to change during failed, partial, or retried responses.
Codex CLI or TUI long-running failures
Requests that continue for 20-50+ minutes, then fail, return partial work, or require manual interruption.
Codex sessions that degrade over time
Sessions that become slow or unreliable and return to normal only after restart, compaction, or re-authentication.
Why This Exists
Paying users need a clear way to document when Codex sessions fail, retry for long periods, or appear to affect request limits and credits without producing usable work. This page collects dated, redacted examples so the pattern can be understood from evidence instead of scattered anecdotes.
Reported concerns
- Usage tokens or credits appearing to increase during automatic retry attempts.
- Failed or incomplete outputs contributing to usage totals.
- Retry behavior extending work without a clear prompt to stop or restart.
- Sessions becoming unreliable without an obvious user-facing signal.
- Users paying for access not receiving enough detail to connect failures with usage changes.
What to Include
Specific, time-bound details are more useful than general impressions.
- Exact error text, retry count, and elapsed time if available.
- Tool used, CLI/TUI/extension version, model, and operating environment.
- Whether the output was usable and whether restarting the session helped.
- Usage total changes, timestamps, screenshots, or redacted logs.
Report template
Short description: Approximate timeframe: Tool used: Model/version: Retry count or elapsed time: Was output usable? Did restarting help? Usage impact noticed: Supporting logs/screenshots:
Submit Your Experience
This form sends a structured report to the collection inbox. Keep reports factual and redact private prompts, credentials, customer data, repository secrets, and confidential logs.
Common Questions
These answers keep the collection scope clear for users arriving from search or social posts.
What Codex problems are being collected?
Reports about stream disconnects, automatic retries, long-running failed responses, degraded sessions, and usage or credit changes observed during those failures.
Can screenshots be submitted?
Yes. The form accepts up to five redacted image files per report, with each screenshot limited to 5 MB.
What should be redacted?
Remove API keys, secrets, private prompts, customer data, repository details, account identifiers, and anything confidential before submitting a report.
Does this page make legal claims?
No. This is a neutral user-experience collection page intended to identify patterns and organize factual reports.
Important Note
This page collects user experiences to identify patterns related to Codex reliability and usage behavior. It does not make legal claims, determine fault, or verify individual billing outcomes. The goal is to understand whether the issues are isolated or more widespread.