Possible Codex usage metering anomaly on Plus (very small tasks consuming large 5h + weekly quota)

[Superfishintights]

What version of Codex CLI is running?

v.0.106.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.3-codex

What platform is your computer?

Linux 6.18.8-3-cachyos x86_64 unknown

What terminal emulator and version are you using (if applicable)?

Kitty

What issue are you seeing?

Codex usage/quota appears to be draining abnormally fast on my Plus account. On March 1, 2026, very small tasks seem to consume a disproportionately large amount of my 5-hour limit. Example: a tiny one-line Kitty config change appeared to consume about 2% of my 5h budget. This feels inconsistent with normal behavior, and especially surprising during the expected 2x allowance period through April 2, 2026.

Other tasks today also decreased my 5hourly and weekly rapidly - usually I have to go nuts on xhigh to get to around 50% but today it just plummeted without even doing a huge amount of usage (no compaction or anything).

What steps can reproduce the bug?

1. Open Codex CLI (v0.106.0) on Plus.
2. Use model gpt-5.3-codex with reasoning medium and summaries auto.
3. Perform a very small request (example: add one config line to Kitty: scrollback_lines -1).
4. Check the usage meter in-session (5h/weekly limits).
5. Observe a large 5h drop (around 2% for this tiny change).

What is the expected behavior?

I'd probably not expect it to drop even 1% on the 1x usage, nevermind 2% on 2x usage allowance.

Small, low-complexity edits should consume only a small amount of the 5-hour quota. Usage drain should feel proportional to task size, and promo/multiplier behavior should be reflected correctly.

Additional information

• Date observed: March 1, 2026
• Account plan: Plus
• Session ID: 019cab03-5403-7d53-96d5-3808d40d607b
• Environment snapshot at time of report:
  • Model: gpt-5.3-codex (reasoning medium, summaries auto)
  • Context window: 14.6K used / 258K (99% left)
  • 5h limit: 37% left (reset shown at 20:38)
  • Weekly limit: 46% left (reset shown at 18:53 on 3 Mar)
• Please verify whether my account is correctly receiving the expected 2x allowance through April 2, 2026 and whether metering is functioning normally.

Note - as I see there's a few other similar threads, I was using subagents, but only to breakdown tasks into smaller tasks as this should've reduced context usage. While I appreciate nothing has obviously been changed - the above example should be pretty clear it's not a 2% usage on 2x limits. I'd be disappointed if it was 2% usage on 1x limits - it was a minor change. It's definitely not normal.

Similar reports found here - similar behaviour to what is shown above.

https://www.reddit.com/r/codex/comments/1rhso58/did_sam_slashed_codex_limits_7x_faster_usage_burn/
https://www.reddit.com/r/codex/comments/1rhw43o/my_codex_tokens_suddenly_have_been_exhausted_over/

[github-actions]

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• Codex usage got decreased by 2-4 times. #13167
• Double usage limits removed on my account? #12759
• Rate Limits Draining Faster #12728
• Entire 5-Hour + 22% Weekly Limits + All Credits Burned Without Running #11508
• 2x Rate Limits not implemented #11785

Powered by Codex Action

[etraut-openai]

As I mentioned on other threads, we have not changed anything on the server side related to usage accounting or metering. If you're noticing a change in usage, it's likely in how you're using Codex.

If you suspect this might be a client-side regression, you could try downgrading to an earlier version of the CLI to see if you observe the same behavior.

[Superfishintights]

As I mentioned on other threads, we have not changed anything on the server side related to usage accounting or metering. If you're noticing a change in usage, it's likely in how you're using Codex.

If you suspect this might be a client-side regression, you could try downgrading to an earlier version of the CLI to see if you observe the same behavior.

Is there no chance a bug has developed that has impacted this in some way unintentionally, as opposed to a direct change?

You can surely agree that the above example (I can screenshot the entire session) should not use 2% on gpt-5.3-codex-medium, especially on 2x?

Usually I'm messaging on high/xhigh with tools, recursive tasks etc. and I'm surprised to see it go below 90% after extensive use. Today I've taken it to below 35% in a 5 hour window of pretty casual usage and with lower reasoning.

I'll see if I can downgrade, but I think there's been enough people suddenly comment on the issue in the last 24-48 hours that something might be playing up somewhere - even if unintentionally. I just don't want to assume "it's me" and it lead to a bigger issue as right now I feel loathe to use it because it decimates my usage allowance. Prior to today, even on Plus it felt like I had near unlimited usage based on the stats.

[Ixe1]

I'm also noticing a strange synchronisation issue with my weekly % which I haven't previously noticed for some time. In the attached screenshot, for example Codex CLI initially said 56% which is aligned with the website, then less than a minute later while processing my prompt it suddenly changes to 53% weekly in Codex CLI (screenshot), while the website still says 56% weekly, and then Codex CLI moments later also goes back to 56% weekly. I'm not sure if this in some way related to some issues others are reporting about a sudden change in consumption of the quota, but thought I'd share this in case it's useful or important in some way.

I'm on Pro plan.

[dhaern]

As I mentioned on other threads, we have not changed anything on the server side related to usage accounting or metering. If you're noticing a change in usage, it's likely in how you're using Codex.

If you suspect this might be a client-side regression, you could try downgrading to an earlier version of the CLI to see if you observe the same behavior.

Im really tired of your useless replies in every similar issue when this is full of users reporting the same thing here and on Reddit... so STOP with your 0 help and say to your supreme leader Sam Altman to stop laugh at his customers because we are paying big amounts of money and restore back our normal usage limit and fix your apps... this is unaceptable and reading people like you is annoying.

[flier268]

正如我在其他帖子中提到的，我們沒有對伺服器端與使用量統計或計量相關的任何設定進行更改。如果您發現使用量發生變化，很可能是您使用 Codex 的方式改變了。

如果您懷疑這可能是客戶端回歸問題，您可以嘗試降級到早期版本的 CLI，看看是否會出現相同的行為。

You only need to fix this bug where there's remaining credit but it can't be used; you don't need to worry about whether our usage method has changed.

[isekaishy-jpg]

Going to add, Using Win 10/vscode extension. Usage of 5h/weekly was insanely high compared to previous week. There's clearly something wrong.

[almaz1011996]

I also ran into this problem. On February 24, everything was fine. And the next time I used Codex on February 28, the limits started to be used up very quickly. Today I also tried to install an older version of the Codex CLI, but the problem still remains. Apparently, the problem is on the server side, the principle of counting tokens/limits has changed.

[devtrf]

Same here.

Definitely something going on here - what used to last 2/3 days now lasts 2/3 hours.

[finanzenkutz-tech]

same here

[isekaishy-jpg]

seems likely? https://www.reddit.com/r/codex/comments/1rhw43o/my_codex_tokens_suddenly_have_been_exhausted_over/
i consumed 30 credits on an rg and two reads totalling 800 loc and a git diff earlier.