Repository navigation
Limits – Reduced usage after 20 minutes. #15073
Description
What version of Codex CLI is running?
codex-cli 0.115.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.4 high
What platform is your computer?
Linux 6.8.0-106-generic x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
Tabby
What issue are you seeing?
Today, my credits on my account user-grEQqq7dokHb56wxlYbBeUWO reset correctly at 5:50 PM CEST and all usage limits were back at 100%. However, while I was running a task, I noticed it was consuming far more than normal. Specifically, from around 6:10 PM CEST to about 6:30 PM CEST, so within roughly a 30-minute window, I used up all of the 5-hour limits and 30% of the weekly limits.
The x2 promo has not ended yet, so I do not think that is the reason. This concerns me even more for when it does end, because at this rate the Pro account will basically become the new Plus account.
I have attached the thread from my session, and I hope you can review it to identify the issue that occurred, because it is clear that there is some kind of problem. I have never consumed this much in 30 minutes, not even when pushing it to the maximum.
What steps can reproduce the bug?
Uploaded thread: 019d01f1-2bc3-75a0-a802-5b2c4c585cb6
What is the expected behavior?
No response
Additional information
As you can see from the photo, the usage section doesn’t show the full peak in usage either, whereas the main section does:
Activity
github-actions commentedon Mar 18, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
etraut-openai commentedon Mar 18, 2026
Please refer to #14593.
Sokalledcoder commentedon Mar 18, 2026
I am experiencing the same issue described above, and I have seen it on both Plus and Business accounts, not just Pro.
In my case, usage limits appear to be dropping unusually fast. I can send only a small number of prompts, sometimes as few as five, and watch the weekly limit decrease prompt by prompt. Because of how consistently this is happening, it seems like there may be a real issue after version v0.115.0 rather than isolated user confusion.
Another unusual detail on my account is that my usage breakdown was categorized as “Other,” even though I only use the Codex CLI on Linux and Windows 10. In the past, the exact same workflow was always recorded as CLI, so this change is unexpected and may be related.
I am mentioning this both to confirm that another user is seeing the same behavior and to encourage a closer investigation. Referring people back to threads from several days ago does not really address what appears to be an active and wider problem. At this point, it seems likely that multiple users are being affected.
YoloMark98 commentedon Mar 18, 2026
If you're using gpt-5.4, this will consume usage about 30% faster than gpt-5.3-codex.
If you use "fast mode", this will consume usage at a 2x rate.
If you use the large context window (a new experimental feature available with gpt-5.4), this will consume usage at a 2x rate.
If you enable the experimental multi_agent feature, subagents will typically consume tokens at a higher rate than if you are not using subagents. As we continue to refine this experimental feature, some changes may affect token consumption. If you are concerned about usage consumption, leave this feature in its default (disabled) state for now.
Manually enabling feature flags for features that are still under development may consume tokens at a much higher rate. We don't recommend doing this.
Please check my chat of thread id attached.
YoloMark98 commentedon Mar 18, 2026
Many people are saying here #14593 (comment) that the issue is always down to CODEX; in other words, too many ‘sessions’ mean that more tokens are being used somehow – perhaps because every agent that is run takes a sort of summary of all the sessions? Is this perhaps why credits are being used up so quickly?
You absolutely must look into this, as we users cannot afford to lose so much usage over an error that has now almost been identified.
YoloMark98 commentedon Mar 18, 2026
@etraut-openai
SarthakYadav commentedon Mar 18, 2026
@etraut-openai Before writing off what users are saying, you ought to do a better job of checking into the issues. I just upgraded but still couldn't use my account, even when I could see 100% usage remaining. Deleted my sessions folder and it worked. There is a bug, at least acknowledge it.