Selected model is at capacity. Please try a different model.
Open 💬 4 comments Opened Jul 17, 2026 by raterolfrontback
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
latest
What subscription do you have?
Pro 20x
Which model were you using?
gpt-5.6 high
What platform is your computer?
windows11
What terminal emulator and version are you using (if applicable)?
_No response_
Codex doctor report
What issue are you seeing?
Selected model is at capacity. Please try a different model. Every time the codex will stop working
What steps can reproduce the bug?
Just ask a question use my previous model (not happened every time but happened 3 times for me in the previous 1 hour) and it said "Selected model is at capacity. Please try a different model."
What is the expected behavior?
Model should be working
Additional information
_No response_
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Im getting this too, using Pro 5x ,theres no warning or graceful completion of task , it just halts with no warning, multiple continues required at times or starting over in a new conversation
This queue issue a big one because often it will break the prompt with this capacity issue presumably from a load balancer but then it will cascade right into the follow up tab queued prompt even though that prompt is/can be dependent on the previous prompt having finished correctly
for example, if ive prompted implement and merge A which fixes B and then tab queued up "now that B is fixed we can implement C" then "selected model is at capacity" hits, it can immediately halt our finishing of A but then because a load balancer switches us to somewhere where the model is not at capacity, it can from a dirty halfdone feature A begin the confused implementation of C from a partially done conversation.