Codex Desktop completely unusable for one week - all models show "Selected model is at capacity" on Pro 20x plan
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
Codex App version: [Please replace with your actual version from About Codex]
What subscription do you have?
Codex Desktop: new
What platform is your computer?
Microsoft Windows NT 10.0.26100.0 x64
What issue are you seeing?
Codex App has been completely unusable for approximately one week.
When running any Codex task, the request fails with the following error:
"Selected model is at capacity. Please try a different model."
The issue happens continuously and is not limited to a specific model.
I have tried switching between different available models in Codex, but every selected model produces the same error.
Example error:
Selected model is at capacity. Please try a different model.
This prevents Codex from executing any coding task.
The problem started approximately 7 days ago and still occurs at the time of reporting.
No PII is included.
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a08006-2a95-7d43-9045-459cba092401
What is the expected behavior?
Expected behavior:
Codex should successfully start the selected model and execute the coding task.
Changing between available models should allow the user to continue working if one model is unavailable.
A Pro 20x subscription should provide reliable access to Codex functionality.
Additional information
Additional information:
- This issue has persisted for about one week.
- Restarting Codex App does not resolve the issue.
- Restarting the computer does not resolve the issue.
- Logging out and signing in again does not resolve the issue.
- Switching models does not resolve the issue.
- The problem affects all Codex model selections.
This appears to be a service-side availability, routing, or account entitlement issue rather than a local configuration problem.
Screenshots can be provided if needed.
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
Start by reproducing the failure on Windows with the Pro 20x subscription and Feedback ID no-active-thread-01a08006-2a95-7d43-9045-459cba092401. Investigate the reported service-side availability, routing, or account-entitlement behavior; done means Codex can execute a task and switching models no longer produces the capacity error.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100