codex - 💡(How to fix) Fix Codex says limit reached even though usage still shows 2% remaining [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#18355Fetched 2026-04-18 05:55:22
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3closed ×1commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

What issue are you seeing?

Codex shows that I still have 2% of usage remaining, but when I try to send a new prompt it says I have already reached the maximum limit.

<img width="613" height="892" alt="Image" src="https://github.com/user-attachments/assets/ae18518e-512e-40e1-96bf-cb1f86ced1dc" />
<img width="1276" height="240" alt="Image" src="https://github.com/user-attachments/assets/3d39bffb-3547-4b9c-a897-cde55924a82d" />

What steps can reproduce the bug?

  1. Open Codex with usage showing 2% remaining.
  2. Try to send a new prompt.
  3. Codex blocks the request and says the maximum limit has already been reached.

What is the expected behavior?

If usage still shows 2% remaining, Codex should allow new prompts until the limit is actually reached.

Additional information

No response

extent analysis

TL;DR

The issue may be resolved by checking for any hidden or pending usage that is not reflected in the displayed 2% remaining, as this discrepancy could be causing Codex to block new prompts prematurely.

Guidance

  • Review the usage metrics and limits documentation for Codex to understand how usage is calculated and what factors might contribute to the discrepancy between the displayed usage and the actual limit.
  • Investigate if there are any background or asynchronous processes that could be consuming usage without being immediately reflected in the displayed percentage.
  • Check if there's an option to refresh or update the usage display manually, which might help synchronize the shown usage with the actual state.
  • Consider reaching out to Codex support for further assistance, as they may be able to provide more detailed insights into the usage tracking and limit enforcement mechanisms.

Example

No specific code example can be provided without more context on how Codex integrates with the user's application or how usage is tracked and reported.

Notes

The solution or workaround may depend on the specifics of how Codex tracks and updates usage, which is not fully detailed in the provided information. Additionally, the presence of any caching or delay in updating the usage display could contribute to the observed issue.

Recommendation

Apply workaround: Given the information, it seems more likely that there's a need to understand or work around the usage tracking and display rather than an issue that can be resolved through an upgrade, assuming such an option is even available.

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

codex - 💡(How to fix) Fix Codex says limit reached even though usage still shows 2% remaining [1 comments, 2 participants]