openai / openai/codex

Unusually high codex usage with one small task

Open
#42,997 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug rate-limits
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.901.41600

What subscription do you have?

plus

What platform is your computer?

windows

What issue are you seeing?

Hi OpenAI Support Team,

I want to raise an issue regarding unusually high Codex usage consumption on my account.

I have noticed that my Codex usage is draining much faster than before. Earlier, a typical Codex usage/session used to reduce my weekly usage by around 12–14%. However, in my last usage, the weekly usage suddenly dropped from around 35% to 1% in a single 5 hr usage, which seems unusually high.

Now I noticed another issue: even before the actual conversation/work properly started, my 5-hour usage limit dropped to around 86% in one go, right after the first message without doing any activity. This looks abnormal because there was no heavy task or extended interaction at that point.

Request you to please investigate the following:

Whether Codex usage is being calculated correctly for my account.
Why a single usage caused such a large drop compared to previous usage patterns.
Why the 5-hour usage limit dropped heavily even before meaningful conversation/work started.
Whether there is any bug, stuck session, background process, or incorrect usage accounting affecting my account.
Whether the usage can be reviewed and corrected if it was charged incorrectly.
This is making Codex difficult to use, because the usage limit is getting exhausted far faster than expected.
Thanks.

What steps can reproduce the bug?

usage as agent to post on my website

What is the expected behavior?

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is named; the report only identifies Codex App 26.901.41600 on Windows and an agent task. Start by locating the usage-accounting path and determine how the first message and five-hour session are recorded; done means explaining or correcting the reported discrepancy with a reproducible check.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.