openai / openai/codex

Why can't I use my 5.3 that's full?!

Open
#45,566 2 comments 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)?

Version 26.908.40834

What subscription do you have?

PRO

What platform is your computer?

Windows

What issue are you seeing?

I want to know why can't I use my full 5.3 access when I'm paying for PRO. Am I being scammed by not having access when It's fully available?

GPT-5.3-Codex-Spark usage limits
5 hour usage limit
Resets 2:37 AM

100% left
Weekly usage limit
Resets Sep 21, 2026, 9:37 PM

100% left

What steps can reproduce the bug?

Feedback ID: no-active-thread-01a0a2b7-8658-7fa1-9ee2-316e4c075ab7

What is the expected behavior?

To have access to something I paid for

Additional information

I should have access to this feature or I should receive a refund for being frauded

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

No source file, test, or reproducible steps are provided. Start by checking the PRO entitlement and GPT-5.3-Codex-Spark usage-limit behavior for Codex App version 26.908.40834 on Windows, using feedback ID no-active-thread-01a0a2b7-8658-7fa1-9ee2-316e4c075ab7. Done means the access restriction is explained or the reported entitlement behavior is corrected.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
authorization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.