Possible Codex usage/reset bug — unexpected drop from 98–99% to 16% after a reset
Nobody has claimed this yet.
- 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.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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with Feedback ID 01a08710-779c-7b53-abbd-e25d544bb640 and the reported reset/restart sequence, using app version 26.903.61454 and Darwin 25.6.0 arm64 as context. Check the usage and reset records for the account and affected period. Done means the discrepancy is explained and any inaccurate balance or reset credit is corrected.
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
- 28/100