Usage dropped from 78% to 3% out of nowhere
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 plan
What platform is your computer?
Mac OS
What issue are you seeing?
My Codex usage suddenly dropped from 78% to 3% today, September 9, 2026.
At around 7 PM, I still had roughly 78% of my weekly usage remaining. I’ve only been running a single GPT-6 Astra thread with one agent doing some minor work. Then, out of nowhere, I got a popup saying I only had 3% of my weekly usage left.
That doesn’t seem possible at all. There’s no way a single thread doing light work could have used around 75% of my weekly allowance that quickly. This looks like a usage tracking or billing issue.
I opened a support ticket through the support, page but this has now automatically been closed!
What steps can reproduce the bug?
My Codex usage suddenly dropped from 78% to 3% today, September 9, 2026.
At around 7 PM, I still had roughly 78% of my weekly usage remaining. I’ve only been running a single GPT-6 Astra thread with one agent doing some minor work. Then, out of nowhere, I got a popup saying I only had 3% of my weekly usage left.
That doesn’t seem possible at all. There’s no way a single thread doing light work could have used around 75% of my weekly allowance that quickly. This looks like a usage tracking or billing issue.
I opened a support ticket through the support, page but this has now automatically been closed!
What is the expected behavior?
Additional information
No response
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
No repository files, tests, or reproducible trigger are identified. Start by tracing weekly usage and quota reporting for the Pro plan, using the reported Codex App version and the change from 78% to 3%; done means the discrepancy is reproduced or explained and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- backend, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100