codex - 💡(How to fix) Fix Inconsistent quota display and premature usage-limit error in Codex CLI 0.120.0 [1 comments, 2 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#17537Fetched 2026-04-13 05:38:48
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4closed ×1commented ×1

Codex CLI 0.120.0 shows inconsistent quota information and then reports usage_limit_exceeded.

Error Message

  • The red banner says Error running remote compact task: You've hit your usage limit. To get more access now, send a request to your admin or try again at Apr 13th, 2026 12:46 AM. The status UI and the error state do not agree. The limit warning, /status, and the error banner present different remaining quota values, which makes it hard to understand whether the account is actually out of quota or the client is reading stale/inconsistent state.

Root Cause

Codex CLI 0.120.0 shows inconsistent quota information and then reports usage_limit_exceeded.

RAW_BUFFERClick to expand / collapse

Summary

Codex CLI 0.120.0 shows inconsistent quota information and then reports usage_limit_exceeded.

What I observed

  • The TUI status line shows 5h 1% • weekly 69%.
  • /status shows 99% left (5h) and 84% left (weekly).
  • The red banner says Error running remote compact task: You've hit your usage limit. To get more access now, send a request to your admin or try again at Apr 13th, 2026 12:46 AM.

Local trace

I traced the local session history for 019d7b9b-7c4c-72f2-a821-9a3c003fb61c in C:\Users\khanhtd\.codex\sessions\2026\04\11\rollout-2026-04-11T15-14-40-019d7b9b-7c4c-72f2-a821-9a3c003fb61c.jsonl.

Relevant snapshots:

  • 2026-04-11T08:35:52.171Z: primary.used_percent=1.0, secondary.used_percent=2.0
  • 2026-04-12T13:10:35.221Z: primary.used_percent=1.0, secondary.used_percent=16.0
  • 2026-04-12T14:07:47.435Z: usage_limit_exceeded

Why I think this is a bug

The status UI and the error state do not agree. The limit warning, /status, and the error banner present different remaining quota values, which makes it hard to understand whether the account is actually out of quota or the client is reading stale/inconsistent state.

extent analysis

TL;DR

The inconsistent quota information and usage_limit_exceeded error may be resolved by checking the actual quota usage and limits through an admin request or waiting until the specified reset time.

Guidance

  • Verify the current quota usage and limits through official channels or admin requests to determine the actual remaining quota.
  • Compare the quota usage reported by the TUI status line, /status command, and the error banner to identify any discrepancies.
  • Check if waiting until the specified reset time (Apr 13th, 2026 12:46 AM) resolves the usage_limit_exceeded error.
  • Review the local session history to ensure that the quota usage is being accurately tracked and reported.

Example

No code snippet is provided as the issue does not involve code-related fixes.

Notes

The provided information suggests a potential issue with the Codex CLI's quota tracking and reporting mechanisms. However, without further details on the underlying system and quota management, it is difficult to provide a definitive solution.

Recommendation

Apply workaround: Wait until the specified reset time (Apr 13th, 2026 12:46 AM) to see if the usage_limit_exceeded error is resolved, as the error banner suggests that the quota will be reset at this time.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING