openai / openai/codex

GPT-5.3-Codex-Spark quota shows 100% remaining but model is missing from Codex selector

Open
#46,144 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

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

26.911.61220

What subscription do you have?

Pro

What platform is your computer?

No response

What issue are you seeing?

My GPT-5.3-Codex-Spark usage page shows 100% remaining for both the 5-hour and weekly Spark limits. However, GPT-5.3-Codex-Spark does not appear in the Codex model selector.

My regular Codex and Work usage limit is exhausted, and the app asks me to add credits or wait for the regular quota reset. Since the Spark allowance is shown as separately available at 100%, I expected to be able to select and use GPT-5.3-Codex-Spark, but the model is not available in the selector.

The model selector currently shows Default, GPT-6 Astra, GPT-5.6 Sol, GPT-5.6 Terra, GPT-5.6 Luna, and GPT-5.5, but no GPT-5.3-Codex-Spark.

Please check whether the Spark entitlement or model availability is not syncing correctly with my account.

What steps can reproduce the bug?

Feedback ID: 01a02dbb-c2d2-74b1-8b8c-de284117ae76

What is the expected behavior?

No response

Additional information

No response

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

Start with the reported Feedback ID 01a02dbb-c2d2-74b1-8b1b-8b8c-de284117ae76 and trace how account entitlements reach the Codex model selector. Confirm why GPT-5.3-Codex-Spark is absent despite both Spark quotas showing 100% remaining; done means an eligible Pro account can select the model or receives an accurate availability state.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.