openai / openai/codex

Persistent "Selected model is at capacity" error prevents Codex usage

Open
#46,205 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Description

I am consistently receiving the following error when trying to use Codex:

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

The issue is persistent rather than intermittent and is currently preventing me from using the selected model normally.

I would appreciate it if the team could confirm whether this is caused by model capacity, an account-level model access restriction, or another Codex-side issue.

Actual behavior

When I attempt to start or continue a Codex task, the request fails with:

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

Repeated attempts continue to produce the same result.

Expected behavior

The selected model should be available normally, or the UI should clearly indicate whether the issue is caused by:

  • temporary model capacity
  • usage/rate limits
  • account eligibility/access restrictions
  • another service-side limitation
Impact

This currently prevents me from using Codex normally and significantly affects my workflow.

Additional information

I can provide the following privately to OpenAI Support if needed:

  • account email
  • exact timestamps
  • screenshots
  • selected model
  • Codex client/version
  • request or diagnostic IDs

Please let me know what diagnostic information would be most useful for investigating this issue.

Screenshot

I have attached a screenshot showing the error.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report does not identify a repository file, test, or entry point; it describes a persistent service-side capacity or access error. Start by determining whether this repository handles the reported error, and use the supplied model, client version, timestamps, and diagnostic IDs to reproduce or classify it. Done would require a confirmed cause and a repository change, but no such change is specified.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.