App Quota Lock Glitch. Stale/Invalid Rate Limit Displayed (Stuck on Lagged Date)

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

Version 26.623.30605 • Released Jun 25, 2026

What subscription do you have?

Go

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What issue are you seeing?

My local desktop client has completely locked up the composer interface with a broken rate-limit banner.
The banner states: "You're out of Codex messages. Your rate limit resets on Jul 25, 2026."

This date doesn't makes any sense. My messages originally ran out at 18:12 on July 25th, and the current time is already 01:21 AM on July 26th.

The application is aggressively enforcing a hard, glitched block screen pointing backwards into yesterday's date window instead of clearing the barrier upon timestamp expiration.

Steps Taken That Failed to Resolve the Bug:
Uninstalled and Reinstalled: Completely removed the application from Windows and reinstalled it from scratch. The broken error screen reappeared instantly upon reinstallation.
Logged Out and Back In: Logged out of my Go Tier account inside the app UI and logged back in. The application immediately fetched the same stale, broken rate-limit status.
Checked local app root directory binaries (AppData\Local\OpenAI\Codex\bin and runtimes). No flat auth.json or config cache parameters are exposed in this namespace to wipe manually.

Please check my account state server-side to forcefully clear this cached token blockage, or provide insight into where this packaged version caches its local user data so I can wipe it.

<img width="1918" height="1078" alt="Image" src="https://github.com/user-attachments/assets/fddd10b5-512c-4b91-b6d4-3400a5bbe02d" />

<img width="380" height="696" alt="Image" src="https://github.com/user-attachments/assets/badaade2-cf6f-4779-bb7e-ac02e8689781" />

What steps can reproduce the bug?

One time bug that i cannot fix.

What is the expected behavior?

I expeceted the desktop application to refresh its local message entitlement check automatically. Once the system clock passes the specific block timestamp, the application composer lock should unlock immediately without forcing a rigid UI hang or showing stale retroactive dates for Go Tier users.

Yet it's still stuck on 5:47pm from yesterday and i cannot use the app at all.

Additional information

email used:
aasif.radim@umail.utm.ac.mu