Selected model is at capacity. Please try a different model Please take this seriously and provide a clear solution.
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)?
26.908.70816
What subscription do you have?
pro20x
What platform is your computer?
macos Darwin 25.6.0 arm64 arm
What issue are you seeing?
It happens every time on my account. "Selected model is at capacity. Please try a different model." i changed every model ,it show the same issue. Feedback ID:01a0aa1e-ac3f-7711-b510-cca09d99847f
What steps can reproduce the bug?
Feedback ID:01a0aa1e-ac3f-7711-b510-cca09d99847f
What is the expected behavior?
Feedback ID:01a0aa1e-ac3f-7711-b510-cca09d99847f
Additional information
I've been using GPT for a long time, and only recently started noticing what feels like a real drop in quality or intelligence.
I've always trusted you guys to provide the level of service and quality users should be able to expect. I also genuinely believe that better
collaboration between people and Al can help us do better work and, in some small way, make the world a better place.
So, if there's any chance you can press the 'back to normal effort/model' button on your side, I'd be incredibly grateful."
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 with the reported Feedback ID 01a0aa1e-ac3f-7711-b510-cca09d99847f and the repeated capacity error across models. The report names no source file, test, or reproducible steps; done would require identifying the account-side cause and documenting a confirmed resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100