Repository navigation
Possible Codex usage/reset bug — unexpected drop from 98–99% to 16% after a reset #44206
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.903.61454
What subscription do you have?
PRO x20
What platform is your computer?
Darwin 25.6.0 arm64 arm
What issue are you seeing?
Subject: Possible Codex usage/reset bug — unexpected drop from 98–99% to 16% after a reset
Hi Codex Support Team,
I’m a Pro subscriber using the Codex desktop app. I’d like to report a possible usage-reset or usage-reporting bug and request that my reset credit be restored, along with appropriate compensation for the disruption.
This happened approximately within the last one to two hours. I don’t have the exact timestamps, but the sequence was:
- While Codex was actively working on a task, it reported that my usage limit had been reached and stopped working.
- I clicked Reset at the bottom of the conversation, using one of my usage-reset credits.
- After the reset, the app still showed 0% remaining.
- I restarted Codex, and the remaining usage then showed 100%.
- After a brief conversation and one work session, it showed approximately 98% or 99% remaining. I don’t recall the exact percentage.
- Shortly afterward, the remaining usage unexpectedly dropped to 16%. This seemed inconsistent with the limited work I had just performed.
- I restarted Codex again, but the usage stayed at 16%.
The attached screenshot shows the 16% remaining state. It documents the current display; I don’t have screenshots of every earlier step.
There appear to be two issues: the reset initially failed to update the displayed usage until I restarted the app, and the newly restored allowance subsequently dropped sharply without an explanation. I cannot determine whether this was a display synchronization problem, a usage-accounting issue, or something else.
This interrupted my ongoing work, cost me productive time, and required additional restarts and troubleshooting. It also appears to have wasted one of my reset credits, since the restored allowance did not remain available as I expected.
I’m requesting that you:
- Investigate the reset and usage records to explain what happened, including whether the reset was applied correctly and what caused the sudden drop.
- Correct any inaccurate usage balance and restore the reset credit used during this incident.
- Provide appropriate additional compensation, such as usage allowance or a service credit, for the interruption and lost productive time.
If you need more information, please tell me exactly what would help—for example, my app version, operating system, affected conversation or task IDs, approximate timestamps, or diagnostic logs—and how to provide it securely.
Thank you. I’d appreciate a clear explanation and a resolution addressing both the usage discrepancy and the reset credit.
What steps can reproduce the bug?
Feedback ID: 01a08710-779c-7b53-abbd-e25d544bb640
What is the expected behavior?
No response
Additional information
my codex account
aivorx
@aivorx
login method gmail
drinkle1226@gmail.com
Activity
github-actions commentedon Sep 9, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
dmognaschi commentedon Sep 9, 2026
The same to me: from 30% to 0% in a single prompt a few minutes ago.
gmercey commentedon Sep 9, 2026
same here: from 70% to 20% while using astra light with one simple prompt and quick answer (not fast mode)
Belgian-Coder commentedon Sep 9, 2026
Same for me went from 99% to 2% after updating the desktop app. looks like it lost the last reset.
exitoenlafamilia commentedon Sep 9, 2026
Same here! After a reset got 13% reduction after a few minutes. Im pro 20x plan
capinfl commentedon Sep 9, 2026
I feels like everyone got their usage vanished. I had GPT6 astra for limited tasks, havign 5.6-sol for the main tasks, even tho I did a weekly reset today it is simply gone after a few hours of usage.
bgyss commentedon Sep 9, 2026
This happened overnight for me on a Plus membership - I only run 2 everyday automations and my weekly went from ~80% to 7% between 11pm and 10am this morning.
Here's my feedback ID in case anyone at OAI is interested in my logs: no-active-thread-01a0872c-a7fd-7201-841e-d192ab67f907
xXAvoraXx commentedon Sep 9, 2026
+++
I had the same problem; my Codex limits were full, so I used my reset option. At first, the limit showed as 0%, then it went to 100%. After using it for a bit, it dropped to around 98%, and then immediately went back to 0%.
As a result, I used my reset option, but it was automatically deleted before I could use the entire limit, and it dropped to 0%.
tradesdontlie commentedon Sep 9, 2026
Additional Windows evidence for the September 9 sudden weekly quota loss. User reports roughly 65% -> 8% remaining with no agents running. Local recorded rate-limit payloads substantiate 66% -> 8%, although they do not capture the exact instant of the change.
Environment: Windows x64; ChatGPT/Codex desktop host; bundled codex-cli 0.153.4 (queried directly); plan_type=pro; recent session model gpt-6-astra. Desktop UI version not independently verified. No subagents launched for this investigation.
Exact quota evidence (UTC)
The weekly reset moved EARLIER by 25,891 seconds (7h 11m 31s), alongside a 58 percentage-point increase in used quota. This is the same general Codex weekly bucket, not a comparison against the separate Spark bucket or a five-hour window. Adjacent prior snapshots varied by one second in reset time; that does not explain this seven-hour change.
Local activity checks
Interpretation and limits
This corroborates a quota/accounting/window synchronization discrepancy and is consistent with the other reports today. It does NOT establish a specific backend bug. Possible explanations needing investigation include reset/window reassignment, reset rollback, delayed usage reconciliation, or an allowance denominator change. No claim is made that these are confirmed. Local logs cannot rule out usage on another device/cloud, account/workspace changes, or missing telemetry. No reset action or plan change was independently established in this investigation. We cannot reproduce on demand.
Requested investigation
Please correlate the timestamps with the account-side usage ledger and explain:
This report intentionally excludes authentication data, account identifiers, private prompts, repository content, and raw logs. Detailed local evidence is preserved and can be supplied privately to OpenAI Support if needed.