Account-level "Selected model is at capacity" on 100% of requests across all models (Pro plan)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Environment
- OS: Windows 11 (10.0.26200)
- Codex CLI 0.153.4; the desktop app behaves identically
- Plan: Pro (
chatgpt_plan_type=pro), account idd8927685-…(full id available privately on request) - All tests: 2026-09-17, 07:54–08:05 UTC, one machine, one network
What happens
Every request, on every model, is rejected with:
Selected model is at capacity. Please try a different model.
Model-by-model probe (one minimal request each, --sandbox read-only, low reasoning effort)
| model | result |
|---|---|
| gpt-6-astra | at capacity |
| gpt-5.6-sol | at capacity |
| gpt-5.6-luna | at capacity |
| gpt-reserve | at capacity |
| gpt-5.5 — 3 consecutive attempts | at capacity (3/3) |
gpt-5.5 with service_tier=priority |
at capacity |
| gpt-5.6-terra | stream disconnected before completion, request id 8977beed-af35-4524-8d94-61c25248e952 |
Reproduce: printf 'say OK' | codex exec --skip-git-repo-check -m gpt-5.5 -c model_reasoning_effort=low --sandbox read-only
Ruled out
- Client: CLI and desktop app fail identically
- Client version: the rejection is server-side, not client-side
- Model choice: every model is rejected, including gpt-reserve
- Machine and network: unchanged; no usage-limit message is ever shown, only the capacity rejection
Ask
This looks like account-level admission/routing rather than model-level capacity. Please check this account's admission state, and whether activity-based throttling has been applied to it. The account also runs automated agent workloads, so if admission is limited by account activity, please point me at the applicable limits.
Independent reports describe the same account-level pattern — e.g. #46103: on one machine and one network, one account fails 0/11 while another account succeeds 11/11.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is identified; begin by reproducing the failure with the provided codex exec command and compare the behavior across models and accounts. Review issue #46103 alongside this report, then investigate the account-level admission or routing state. Done means identifying the cause or applicable account limits, rather than changing the CLI client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100