codex - 💡(How to fix) Fix Selected model is at capacity [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19583Fetched 2026-04-26 05:14:27
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Timeline (top)
labeled ×4commented ×2unlabeled ×2
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.422.30944

What subscription do you have?

Pro 200 USD

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Message sayung Selected model is at capacity, even though my token limits are only used 10% of my plan.

I’ve had a session work to test an electorn app’s interfaces and log each window’s errors, and suggest optimization improvements based on log outputs and delays, it Worked for 3h 9m 39s, then stopped suddenly saying Selected model is at capacity.

Then every conversation with GPT 5.5 xhigh on a Pro 200 USD account kept saying the same thing, so i was no longer able to use this model so i had to switch back to 5.4 xhigh to continue my work.

Is it an issue from my side or is this an OpenAI issue? I’ts been2 hours and still the same issue.

What steps can reproduce the bug?

Running 5.5 xhigh on a long running simulation, testing and documentation session (3 hours +).

What is the expected behavior?

Continue working until limit exhaustion or finalization

Additional information

No response

extent analysis

TL;DR

The issue may be resolved by switching to a different model, such as 5.4 xhigh, as the user has already done, or by waiting and trying the 5.5 xhigh model again later.

Guidance

  • The "Selected model is at capacity" error suggests that the issue might be related to the model's usage limits, despite the user's token limits being only 10% used.
  • Try switching to a different model, like 5.4 xhigh, to see if the issue persists.
  • If the issue is specific to the 5.5 xhigh model, it might be worth trying again after some time has passed to see if the capacity issue has been resolved.
  • Verify that the token limits are being accurately reported and that there are no other factors contributing to the model's capacity issue.

Notes

The cause of the issue is unclear, and it's uncertain whether it's a problem on the user's side or an OpenAI issue. The fact that switching to a different model resolved the issue temporarily suggests that it might be related to the specific model being used.

Recommendation

Apply workaround: Switch to a different model, such as 5.4 xhigh, until the issue with the 5.5 xhigh model is resolved.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Selected model is at capacity [2 comments, 2 participants]