codex - 💡(How to fix) Fix Pro weekly usage limit depletes unusually fast on 5.5, worsened by unstable context compaction [8 comments, 6 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#19585Fetched 2026-04-26 05:14:24
View on GitHub
Comments
8
Participants
6
Timeline
15
Reactions
0
Timeline (top)
commented ×8labeled ×4cross-referenced ×2unlabeled ×1
RAW_BUFFERClick to expand / collapse

What version of Codex is running?

Codex app version: 26.422.30944 (2080)

What subscription do you have?

Pro $200

What issue are you seeing?

The weekly usage limit for Pro users appears to be depleting much faster than expected when using Codex with 5.5.

Even without an especially heavy workload, I exhausted almost the entire weekly Pro usage allowance within about two days. Previously, when using 5.4, the weekly allowance was almost never depleted for me, even when my workload was significantly heavier. This makes me suspect that the 5.5 usage accounting / billing behavior may have a problem, or that the current usage cost is not reasonable for Pro users.

As a $200/month Pro subscriber, the weekly limit currently does not feel sufficient to support even two days of normal usage.

Additional related issue: context compaction wastes a large amount of usage

There is also a severe context compaction problem that makes the usage drain worse:

  • Context compaction currently takes a very long time.
  • It is unstable and sometimes fails.
  • When compaction fails, the current session can effectively become unusable.
  • I then have to start a new session and rerun or re-explain the same task.
  • This wastes a large amount of tokens/usage on top of the already-fast depletion.

So the problem is not only the actual coding work consuming usage. Failed or slow context compaction and forced session restarts are also consuming a lot of the Pro weekly allowance.

Expected behavior

  • Pro weekly usage should last a reasonable amount of time for normal Codex usage, especially on a $200/month plan.
  • Usage accounting for 5.5 should be transparent and comparable to previous model behavior, or clearly documented if it is much more expensive.
  • Failed context compaction should not make a whole session unusable or force users to waste large amounts of usage by restarting tasks.

Actual behavior

  • My Pro weekly allowance was almost fully depleted in about two days under normal usage.
  • This was very different from my previous 5.4 usage experience, where the weekly limit was almost never exhausted even under heavier work.
  • Context compaction instability creates additional large usage waste.

Request

Please investigate whether 5.5 usage accounting / rate-limit consumption for Pro users is working as intended, and whether failed/slow context compaction is causing unnecessary usage loss. It would also help to provide more detailed usage breakdowns so Pro users can understand what is consuming the weekly allowance.

extent analysis

TL;DR

Investigate the usage accounting and rate-limit consumption for Pro users in Codex version 5.5 to determine if it is working as intended.

Guidance

  • Review the usage breakdown to identify which specific features or actions are consuming the weekly allowance at an unexpected rate.
  • Compare the usage patterns and costs between Codex versions 5.4 and 5.5 to determine if there are any significant changes.
  • Investigate the context compaction issue and its impact on usage, as it may be contributing to the rapid depletion of the weekly allowance.
  • Consider providing more detailed usage breakdowns to help Pro users understand what is consuming their weekly allowance.

Notes

The issue may be related to changes in the usage accounting or rate-limit consumption in Codex version 5.5, or it could be due to the context compaction problem. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Provide more detailed usage breakdowns to help Pro users understand what is consuming their weekly allowance, while investigating the usage accounting and context compaction issues.

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…

FAQ

Expected behavior

  • Pro weekly usage should last a reasonable amount of time for normal Codex usage, especially on a $200/month plan.
  • Usage accounting for 5.5 should be transparent and comparable to previous model behavior, or clearly documented if it is much more expensive.
  • Failed context compaction should not make a whole session unusable or force users to waste large amounts of usage by restarting tasks.

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 weekly usage limit depletes unusually fast on 5.5, worsened by unstable context compaction [8 comments, 6 participants]