openai / openai/codex

Codex CLI (ChatGPT login, Pro 20x): frequent ‘stream disconnected before completion’ + repeated ‘Selected model is at capacity’ (Request ID 68f16728-07bb-4a24-b7ca-500757169524)

Open
#45,949 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug CLI connectivity rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

I’m using Codex CLI on Linux, authenticated via “Sign in with ChatGPT” (not an API key). My account is on a ChatGPT Pro 20x tier. Starting today, reliability has degraded significantly and is seriously impacting usage.

Problem A — Streaming disconnects (incomplete responses):

  • During normal prompts, the CLI often fails mid-response with: “stream disconnected before completion … An error occurred while processing your request.”
  • This interrupts generation and forces retries; work cannot be completed reliably.
  • Example request ID: 68f16728-07bb-4a24-b7ca-500757169524 (please correlate with my timestamps/time zone).

Problem B — Capacity message blocks the selected model:

  • Frequently see: “Selected model is at capacity. Please try a different model.”
  • This happens repeatedly today (previously rare) and prevents consistent use of the selected model.

Network / environment notes:

  • Initially observed on CERN internal network; I also reproduced after switching to a different network, so it’s not isolated to that network.
  • OS: Linux (CLI). Codex CLI version: (fill in from codex --version)
  • Model selected: (fill in)
  • Approx timestamps + timezone: (fill in)

Expected: Stable streaming responses and model access consistent with my plan.
Actual: Frequent disconnects and repeated capacity blocks; overall experience is not acceptable for a paid Pro-tier workflow.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the CLI entry point by collecting codex --version, the selected model, and approximate timestamps with timezone; the issue also supplies request ID 68f16728-07bb-4a24-b7ca-500757169524 for correlation. No source file or test is identified, and the missing environment details must be filled in before completion can be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, rust
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.