Codex App reports usage limit immediately after upgrading from Free to Plus

Resolved 💬 3 comments Opened Aug 13, 2026 by laeckerv Closed Aug 13, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

Version 26.803.81509

What subscription do you have?

ChatGPT Plus

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

Immediately after upgrading from the Free plan to ChatGPT Plus, I opened Codex and sent one initial prompt.

After that, Codex started refusing further requests with the following error:

You've hit your usage limit. Upgrade your plan or add credits to continue, or try again at Aug 20, 2026, 3:27 PM.

However, /stats reports that I still have 100% of my 7-day usage allowance remaining:

Session:
019ffb09-8df4-74f0-826d-7ab9d54d4123

Context:
16% left (217,024 used / 258K)

7d limit:
100% left
(resets Aug 20)

There is also unusual behavior with the reported reset time.

For example, one attempt returned:

You've hit your usage limit. Upgrade your plan or add credits to continue, or try again at Aug 20, 2026, 3:27 PM.

A retry approximately two minutes later returned:

You've hit your usage limit. Upgrade your plan or add credits to continue, or try again at Aug 20, 2026, 3:29 PM.

The reset timestamp therefore appears to move forward with the current time, remaining approximately 7 days in the future, rather than representing a fixed usage-reset timestamp.

This seems inconsistent with both the /stats output and normal usage-limit behavior.

What steps can reproduce the bug?

  1. Start on the ChatGPT Free plan.
  2. Upgrade the account to ChatGPT Plus.
  3. Open the Codex App.
  4. Send an initial prompt.
  5. Attempt to send another request.
  6. Codex reports that the usage limit has been reached.
  7. Run /stats.
  8. Observe that the 7-day usage limit shows:
7d limit:
100% left
(resets Aug 20)
  1. Retry the failed Codex request after a few minutes.
  2. Observe that the "try again" timestamp has moved forward by approximately the same amount of time.

Example:

3:27 PM attempt:
try again at Aug 20, 2026, 3:27 PM

3:29 PM attempt:
try again at Aug 20, 2026, 3:29 PM

Session ID:

019ffb09-8df4-74f0-826d-7ab9d54d4123

Context usage:

217,024 used / 258K
16% left

7-day usage:

100% left

I had only sent one initial prompt after upgrading to Plus before the usage-limit error appeared.

What is the expected behavior?

After upgrading to ChatGPT Plus, Codex should recognize the Plus subscription and apply the corresponding usage allowance.

If /stats reports that 100% of the 7-day usage allowance remains, requests should not be rejected for exhausting that same usage limit.

If a usage limit actually has been reached, the reported reset timestamp should represent the real fixed reset time rather than moving forward every time the request is retried.

What is the expected behavior?

After upgrading to ChatGPT Plus, Codex should recognize the Plus subscription and apply the corresponding usage allowance.

If /stats reports that 100% of the 7-day usage allowance remains, requests should not be rejected for exhausting that same usage limit.

If a usage limit actually has been reached, the reported reset timestamp should represent the real fixed reset time rather than moving forward every time the request is retried.

Additional information

The timing may be relevant because the issue appeared immediately after upgrading from Free to Plus. This could potentially be related to subscription/entitlement propagation or usage-meter synchronization after the plan change.

The strongest indication that this may be a bug is the combination of:

  • The account was just upgraded from Free to Plus.
  • Only one initial Codex prompt was sent after upgrading.
  • /stats reports 100% of the 7-day limit remaining.
  • Codex nevertheless reports "You've hit your usage limit."
  • The advertised reset timestamp moves forward on each retry instead of remaining fixed.

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 14 days ago

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

  • #38354
  • #37776
  • #37250

Powered by Codex Action

MilkyWay008 · 14 days ago

Same thing happened to me on a plan change \u2014 the app keeps serving the old entitlement until you force it to re-check. Sign out, fully quit, sign back in, and make sure the billing page actually shows Plus live before relaunching. If it still blocks after that, the threads the bot linked (#38354 etc.) are the same family, so it's worth letting the maintainers consolidate there. Oh also, btw, I built a portable Hermes OTG and I run it on USB as my rescue agent; super handy doing quick diagnose & fix, check it, imo it'll help you. https://github.com/MilkyWay008/Hermes-OTG

laeckerv · 14 days ago
Sign out, fully quit, sign back in

That seems to have fixed it. Thanks!