Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Usage limits are exhausted too quickly in the IDE extension [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#18422•Fetched 2026-04-18 05:54:47
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
bagerxxbagerxx
Participants
bagerxxbagerxxgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4closed ×1commented ×1

Error Message

  • help debug an error

Root Cause

I do not currently have a session ID, exact token usage, or context window usage details because the extension does not make this clearly visible to me. That lack of visibility is part of the problem.

RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

26.415.20818

What subscription do you have?

ChatGPT Plus

What platform is your computer?

macOS Darwin 25.4.0 arm64 arm

What issue are you seeing?

Hello,

I want to report a serious issue with Codex usage limits in the IDE extension.

The current quota gets exhausted extremely quickly. In practice, I can only get through one or two coding tasks before hitting the limit, and then I am forced to wait around 5 hours before I can continue. This makes the tool very hard to rely on for actual development work.

What is especially frustrating is that this did not use to feel this restrictive before. The usage now seems to run out much faster than it used to, even during normal coding sessions. From a user perspective, it feels like the limits were tightened significantly, but there is no clear visibility into what exactly is being consumed or why it is being depleted so fast.

Main problems:

  • Usage is exhausted after only a very small amount of work
  • A 5-hour wait is too disruptive for normal coding workflow
  • There is not enough transparency about what counts toward usage
  • The current experience feels much worse than before

To be honest, if this continues, it will become a reason for me to stop using Codex altogether. A coding tool needs to support iteration, debugging, retries, and refinement. If the quota is gone after just a couple of tasks, the product becomes impractical.

Please reconsider the current usage limit behavior, or at minimum provide much clearer visibility into:

  • what exactly is being consumed
  • how much quota is left
  • why usage is being exhausted this quickly

Right now, the limits feel too aggressive and are actively hurting the developer experience.

What steps can reproduce the bug?

  1. Open the Codex IDE extension in VS Code on macOS.
  2. Start a normal coding session.
  3. Ask Codex to complete one or two ordinary coding tasks such as:
    • explain a file
    • modify a function
    • help debug an error
    • make a small refactor
  4. After a very small amount of work, the usage limit is reached.
  5. I then have to wait around 5 hours before I can continue.

This happens during normal usage and does not require unusually large prompts or extreme workloads.

I do not currently have a session ID, exact token usage, or context window usage details because the extension does not make this clearly visible to me. That lack of visibility is part of the problem.

What is the expected behavior?

The IDE extension should support a normal coding workflow without exhausting usage after only one or two ordinary tasks.

Expected behavior:

  • usage should last long enough for a reasonable development session
  • limits should not be reached after minimal use
  • the product should provide clear visibility into what is being consumed
  • remaining usage should be easier to understand before hitting the limit

Additional information

This feels noticeably worse than before. Earlier, the available usage felt much more workable. Now it depletes so quickly that it interrupts normal development.

If this is expected behavior, the current limits are too restrictive for practical use. If it is unintended, it should be investigated.

It would also help to show:

  • remaining usage more clearly
  • what actions consume usage most heavily
  • why the user is being rate-limited so quickly

extent analysis

TL;DR

The Codex IDE extension's usage limit is being exhausted too quickly, disrupting the normal coding workflow, and a reevaluation of the usage limit behavior or clearer visibility into usage consumption is needed.

Guidance

  • Review the current usage limit settings to determine if they have been recently changed or updated, potentially causing the restrictive behavior.
  • Consider providing more transparent metrics on what actions consume usage most heavily, such as explaining files, modifying functions, or debugging errors, to help users understand their usage.
  • Implement a feature to display remaining usage more clearly, allowing users to plan their coding sessions accordingly and avoid unexpected interruptions.
  • Investigate the possibility of introducing tiered usage limits or adaptive quotas that adjust based on the user's coding patterns and subscription plan.

Example

No specific code snippet can be provided without more details on the Codex API or the IDE extension's implementation. However, a potential solution could involve modifying the extension to fetch and display usage metrics, such as:

# Hypothetical example, not based on actual Codex API
usage_data = codex_api.get_usage()
print(f"Remaining usage: {usage_data['remaining']}")
print(f"Usage consumed by last action: {usage_data['last_action_consumption']}")

Notes

The issue lacks specific technical details about the Codex API, the IDE extension's implementation, or the exact changes that may have caused the restrictive behavior. Therefore, the provided guidance focuses on high-level suggestions for improving transparency and usability.

Recommendation

Apply a workaround by requesting clearer visibility into usage consumption and remaining limits from the Codex development team, as the current behavior is too restrictive for practical use and lacks transparency.

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…
#request error#file not found#serialization error#model compatibility#GPU setup

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 Usage limits are exhausted too quickly in the IDE extension [1 comments, 2 participants]