Selected model is at capacity. Please try a different model.

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

26.609.71450

What subscription do you have?

Pro 5x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I am writing to report a persistent issue with the Codex GPT-5.5 model. Over the past hour, I have received the error message 'Selected model is at capacity. Please try a different model' multiple times.

These interruptions have been frequent enough to prevent me from completing even a short development sprint. Given that I have been using the service for less than an hour, the current rate of service disruption is making it impossible to maintain a productive workflow. Please investigate whether there are capacity constraints affecting my account or the model endpoint specifically.

What steps can reproduce the bug?

Uploaded performance trace: 019ea6e8-ebaa-7c73-b0a1-29e8f682b8bb

What is the expected behavior?

No response

Additional information

No response

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

Error running remote compact task: Selected model is at capacity. Please try a different model. #28303
gpt-5.5 capacity errors and recovered session returns with only ~60-70% context left #27149

Powered by Codex Action

Same here: 019ecf29-4e66-7560-9d34-119832dbecea
ChatGPT 5.5 extra high. ChatGPT Pro 20x plan. @openai/codex cli client on Dev Containers (Fedora Sliverblue 44).

me too： ChatGPT 5.5 extra high. ChatGPT Pro 20x plan.

Oh. This is: https://status.openai.com/incidents/01KV7ZT644J4V94GSXMFPY2ANR

me too： ChatGPT 5.5 extra high Selected model is at capacity. Please try a different model.. me ChatGPT Pro 20x plan.

me too： ChatGPT 5.5 extra high Selected model is at capacity. Please try a different model.. me ChatGPT Pro 5x plan.

Adding another data point with explicit quota/account details.

Environment:

Codex Desktop App: 26.609.71450
macOS: 26.5.1
Subscription: ChatGPT Pro 20x
Observed date: 2026-06-16

Models affected:

GPT-5.5 High
GPT-5.5 Extra High / XHigh

Error shown repeatedly:

Selected model is at capacity. Please try a different model.

Important detail: my account still shows plenty of remaining usage in both the 5-hour allowance and the weekly allowance. This does not look like normal quota exhaustion from the user side, but the error is shown repeatedly anyway. It affects both GPT-5.5 High and GPT-5.5 XHigh.

Expected behavior:

If this is regional/model-serving capacity rather than account quota exhaustion, the UI/error message should make that distinction clear.
If a Pro 20x user still has substantial 5-hour and weekly allowance remaining, Codex should either serve the selected GPT-5.5 model, retry with backoff, or provide a clearer availability/region/capacity explanation.
The current message makes it look like switching models is the only remedy, but both 5.5 High and 5.5 XHigh can fail with the same error.

I do not have an in-product /feedback ID from this reporting path, but this is reproducible repeatedly today on the account described above.

As already mentioned they're working on it

https://status.openai.com/incidents/01KV7ZT644J4V94GSXMFPY2ANR

font{ line-height: 1.6; } ul,ol{ padding-left: 20px; list-style-position: inside; } Ok, thx!

…

---- Replied Message ---- From Can ***@***.***> Date 06/16/2026 20:32 To ***@***.***> Cc ***@***.***> , ***@***.***> Subject Re: [openai/codex] Selected model is at capacity. Please try a different model. (Issue #28507) CanRau left a comment (openai/codex#28507) As already mentioned they're working on it https://status.openai.com/incidents/01KV7ZT644J4V94GSXMFPY2ANR —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you commented.Message ID: ***@***.***>

same for me throughout the whole day
019ecad6-cb71-70b1-a2c1-d42c05fe915f

still having this problem, despite being marked as resolved on status webpage

I’m seeing the same issue on Codex Desktop.

Environment:

OS: Windows
Codex Desktop app version: 26.623.61825
Subscription: ChatGPT Plus
Model: GPT-5.5
Time of occurrence: around 6:00 PM KST
Remaining usage:
- 5-hour limit: 87% remaining
- 1-week limit: 81% remaining

Error banner:

Selected model is at capacity. Please try a different model.

Conversation error:

stream disconnected before completion: An error occurred while processing your request. You can retry your request, or contact us through our help center at help.openai.com if the error persists. Please include the request ID 510f4cac-b03c-403f-8598-8a2064c5a115 in your message.

Request ID:

510f4cac-b03c-403f-8598-8a2064c5a115

This happened despite having remaining usage quota, so it was unclear whether the failure was due to temporary GPT-5.5 capacity, quota handling, or a Codex Desktop streaming issue.

lol3

same sol 5.6

+1 Pro 20x
Same for me on gpt 5.6 and gpt 5.5.

+1 Pro 20x Same for me on gpt 5.6 and gpt 5.5.

😂

DITO – the same issue on an UGREEN SMB share.

CODEX
You don’t need to change anything on the UGREEN NAS, and please don’t relax any permissions for me either.
The share is already set up as a writable workspace. The issue lies with my intended patching tool: it freezes when writing via UNC/SMB, even though reading the same files works fine. Adding an extra NAS user, Docker permissions or changing the SMB settings would not effectively resolve this behaviour.
I’ve just tried again via \MyNASdocker-ssd\…; the write operation gets stuck there too. No files were modified.
To tidy up the code, I can therefore either provide you with the finalised content to insert, or we can leave the working configuration as it is. Functionally, it’s already correct; the tidying up only concerns comments and unnecessarily broad CSP rules.

Same Issue

lol3

fixed? how?

It's almost unusable. When is it expected to be fixed? Both ChatGPT and Codex have such a problem.

Getting this error now constantly:

Selected model is at capacity. Please try a different model.

Upgraded to the latest version，The codex is not functioning.

All of you are shadow banned

it means you are not welcomed，please switch to claude

Just switch to Claude

您好，您发给我的信件已经收到~祝您生活愉快！--------------------------------------------厚德致远，博学敦行This is an automatic reply, confirming that your e-mail was received.Thank you

Navigation Menu

Repository navigation

Selected model is at capacity. Please try a different model. #28507

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

What subscription do you have?

What platform is your computer?

What issue are you seeing?

What steps can reproduce the bug?

What is the expected behavior?

Additional information

32 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Selected model is at capacity. Please try a different model. #28507

Description

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

What subscription do you have?

What platform is your computer?

What issue are you seeing?

What steps can reproduce the bug?

What is the expected behavior?

Additional information

Activity

github-actions commented on Jun 16, 2026

piquark6046 commented on Jun 16, 2026

Evopower commented on Jun 16, 2026

piquark6046 commented on Jun 16, 2026

2689508458 commented on Jun 16, 2026

ENJOYMOON commented on Jun 16, 2026

zimodai commented on Jun 16, 2026

CanRau commented on Jun 16, 2026

zimodai commented on Jun 16, 2026

nos1609 commented on Jun 16, 2026

Ronkiro commented on Jun 16, 2026

ChromaticClouds commented on Jun 29, 2026

32 remaining items

Yu03-6 commented on Sep 8, 2026

nwsynx commented on Sep 8, 2026

yangchaoNJ commented on Sep 8, 2026

nickel1991 commented on Sep 8, 2026

LHBL2003 commented on Sep 9, 2026

LeonYew-Ley commented on Sep 10, 2026

HeyErfan commented on Sep 10, 2026

HeyErfan commented on Sep 10, 2026

sulss520 commented on Sep 15, 2026

faithk7 commented on Sep 16, 2026

lixiang4543 commented on Sep 17, 2026

aaiyer commented on Sep 17, 2026

williamxhero commented on Sep 23, 2026

evokelektrique commented on Oct 12, 2026

Evopower commented on Oct 12, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions