Selected model is at capacity. Please try a different model.
Environment & Subscription
- Application: OpenAI Codex Desktop App (macOS/Windows)
- Subscription Tier: ChatGPT Pro ($200/month)
- Models Affected: 5.5, 5.4
The Problem
As a paying Pro user ($200/mo), the Codex desktop application is currently delivering an absolutely unacceptable, broken experience. During multi-tasking workflows, the application repeatedly encounters the following backend failure:
"Selected model is at capacity. Please try a different model."
Instead of handling this backend overload gracefully, the Codex app reacts destructively:
- Subscription Limits are Wasted: The agents send massive context payloads (worktrees, files, thread history). When the server rejects the completion due to capacity, the usage limits/quotas are still deducted from my Pro account. I am losing expensive limits for zero output.
- Context and State are Permanently Lost: The agent thread breaks mid-execution. The context accumulated by the agent is dropped, corrupting the workflow execution state.
- Zero Proactive Notification: The app does not check server health before initiating tasks, leading to mid-pipeline crashes.
Financial & UX Impact
Paying $200 per month implies enterprise-grade reliability or, at the very minimum, fault-tolerant software. Currently, I am paying to lose my context, burn my allowed requests on server-side failures, and manually restart broken pipelines. ### Expected Behavior (Urgent Fixes Required)
- Pre-flight Checks & Graceful Pausing: Codex must verify model capacity before dispatching heavy prompt payloads. If the model is at capacity, the agent execution thread should PAUSE automatically and retry gracefully without breaking the pipeline or dropping context.
- Quota/Limit Rollback: Failures resulting in
503 Service UnavailableorModel at capacityresponses MUST NOT count against the user's daily/hourly Pro limits. - Proactive In-App Alerting: Display a persistent banner inside the Codex UI when models are degraded, rather than letting agents run blindly into brick walls and ruin hours of isolated worktree progress.
Please address how OpenAI plans to compensate Pro users for the wasted quotas and provide an immediate hotfix for context retention during outages.
7 Comments
<img width="635" height="61" alt="Image" src="https://github.com/user-attachments/assets/e313d931-abfe-48af-b44a-ecc860fb6719" />
And why are you closing the discussion without any clear answer and actual solution to the problem?
The team is investigating the incident and working on a fix.
I locked the other issue thread to prevent users from necroposting to a closed issue that is not related to the current incident.
Thanks for the update. Looking forward to the fix.
Please also keep in mind that for Pro users ($200/mo), these incidents aren't just technical — they result in wasted daily limits and quotas since the requests are charged before the 'Capacity' error occurs. Any information on how OpenAI plans to credit back these lost limits for those affected would be appreciated.
Had the same issue. The task just stopped due to model at capacity error.
Yeah, me too
Yeah, I'm get same issue too
This is now mitigated.