codex - 💡(How to fix) Fix 5-hour Codex limit is reached much faster this week despite lower workload ($100 plan) [2 comments, 3 participants]

What version of Codex CLI is running?

codex-cli 0.130.0

What subscription do you have?

$100 paid plan

Which model were you using?

Codex default/current model in the app. I did not intentionally increase model or effort level compared with last week.

What platform is your computer?

macOS 15.7.1 arm64

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

Codex desktop app / zsh

What issue are you seeing?

Starting this week, the Codex 5-hour usage limit is being reached much faster than it was last week, even though my workload is lower.

This feels like a regression in usage accounting, token consumption, or rate-limit calculation. Last week I was doing more work in Codex and could keep working for longer. This week, with less work and fewer/heavier tasks avoided, I am still getting hit by the 5-hour limit very quickly.

This is especially concerning because I am on the $100 paid plan. I would expect a paid plan at that level to support normal Codex usage without the 5-hour limit depleting dramatically faster under a lighter workload.

What steps can reproduce the bug?

1. Use Codex normally on codex-cli 0.130.0.
2. Keep the workload equal to or lower than prior weeks: fewer tasks, less total work, and no intentional increase in model/effort settings.
3. Watch the 5-hour usage limit during the session.
4. Compare the drain rate with last week under heavier Codex usage.

Actual result: the 5-hour limit is reached much faster this week despite a lower workload.

Expected result: with a lower workload and no intentional model/effort increase, the 5-hour usage limit should last at least as long as it did last week, or Codex should clearly show what changed in usage accounting.

What is the expected behavior?

Usage against the 5-hour limit should be roughly consistent for similar or lighter workflows. If Codex changed accounting, model routing, context handling, polling, or another behavior that materially increases limit consumption, the app should make that visible to users.

For users on paid plans, especially the $100 plan, the app should expose enough detail to understand why usage is being consumed so quickly.

Additional information

This appears related to other reports about unexpectedly fast quota consumption, for example #22459. I am filing this separately because the key symptom is a sudden current-week change: I am doing less work than last week, but the 5-hour limit is being reached much faster.