Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Pro plan 5-hour usage limit depleted in ~20 minutes under light Codex workload [4 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19571•Fetched 2026-04-26 05:14:43
View on GitHub
Comments
4
Participants
4
Timeline
10
Reactions
1
Author
vietntvietnt
Participants
GGBondBlueWhaleGGBondBlueWhalegithub-actions[bot]github-actions[bot]joshuanorman134-sketchjoshuanorman134-sketchvietntvietnt
Timeline (top)
commented ×4labeled ×3cross-referenced ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.125.0

What subscription do you have?

Pro $200

Which model were you using?

gpt-5.5 high fast

What platform is your computer?

Darwin 25.3.0 arm64 arm

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

Warp

What issue are you seeing?

My 5-hour usage limit was consumed extremely quickly: it went from 0% to 100% in about 20 minutes, even though I was only running a light workload.

It feels like I were on a Plus subscription, rather than the $200/month Pro plan.

What steps can reproduce the bug?

Uploaded thread: 019dc546-0442-70e1-9527-531b7f58d1a8

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The issue may be related to incorrect subscription plan detection, causing the 5-hour usage limit to be consumed quickly.

Guidance

  • Verify the subscription plan configuration to ensure it matches the expected Pro plan with a $200/month limit.
  • Check the Codex CLI version (0.125.0) for any known issues related to subscription plan detection or usage tracking.
  • Review the uploaded thread (019dc546-0442-70e1-9527-531b7f58d1a8) for any clues on the usage pattern that might be causing the rapid consumption of the usage limit.
  • Compare the usage patterns with the expected behavior of the Pro plan to identify any discrepancies.

Notes

The issue lacks detailed information on the usage pattern and the expected behavior of the Pro plan, making it difficult to provide a definitive solution.

Recommendation

Apply workaround: Verify the subscription plan configuration and review the usage pattern to identify any discrepancies, as the issue may be related to incorrect subscription plan detection.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#container setup#orchestration issue#cache issue#memory leak#API versioning

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Pro plan 5-hour usage limit depleted in ~20 minutes under light Codex workload [4 comments, 4 participants]