Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex monthly subscription vs 5-hour/weekly limits: request for monthly bank or rollover [2 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#19530•Fetched 2026-04-26 05:15:47
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Author
feedback17feedback17
Participants
feedback17feedback17github-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×2closed ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI

What feature would you like to see?

Posting from a separate account for privacy.

I’m a Codex CLI user on Linux, and I want to raise a product feedback issue about Codex monthly subscriptions versus window-based usage limits.

My concern is not only that the limits may be low. The deeper issue is that Codex is sold as part of a monthly Plus/Pro subscription, but actual usage appears to be enforced through shorter windows such as 5-hour and weekly limits.

If unused included usage does not roll over, then users who work in project-based bursts may pay for a full month but only receive practical access to the remaining 5-hour or weekly allowance when they actually use the product.

This affects Plus and Pro users alike. Even if Pro provides 5×, 10×, or 20× more usage, those multipliers may only increase each usage window. They do not necessarily create a monthly bank of included usage.

My request is not only clearer disclosure, but a reconsideration of the entitlement model.

Suggested product improvements:

  1. A monthly Codex usage bank usable anytime during the billing cycle.
  2. Partial rollover of unused weekly allowance within the same billing month.
  3. Partial conversion of unused included usage into Codex credits.
  4. A burst/project-based Codex plan for users who do not use Codex evenly every day.
  5. End-of-cycle grace usage so monthly subscribers are not limited to only the final weekly window after paying for a full month.

At minimum, the CLI, Help Center, and pricing/plan pages should explicitly disclose:

“Codex limits reset at the times shown in /status. Multipliers such as 5×, 10×, or 20× apply to these usage windows and do not create a monthly bank of included usage. Unused included allowance does not carry over between windows or billing cycles.”

But the bigger request is to better align Codex included usage rights with the monthly billing cycle, especially for project-based and burst-use workflows.

Additional information

No response

extent analysis

TL;DR

The user suggests re-evaluating the Codex entitlement model to better align with monthly billing cycles, particularly for project-based and burst-use workflows.

Guidance

  • Review the current entitlement model to identify potential discrepancies between monthly subscriptions and usage limits.
  • Consider implementing a monthly Codex usage bank or partial rollover of unused weekly allowances to better serve project-based users.
  • Evaluate the feasibility of introducing a burst/project-based Codex plan to cater to users with non-uniform usage patterns.
  • Ensure explicit disclosure of usage limits and reset times in the CLI, Help Center, and pricing/plan pages to avoid confusion.
  • Assess the potential benefits of offering end-of-cycle grace usage to monthly subscribers.

Notes

The issue highlights the need for a more flexible entitlement model, but the technical implementation details are not provided. Further discussion with the development team and stakeholders is necessary to determine the best course of action.

Recommendation

Apply workaround: Implement explicit disclosure of usage limits and reset times in the CLI, Help Center, and pricing/plan pages to improve transparency and avoid user confusion, while further evaluating the proposed changes to the entitlement model.

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…
#runtime error#dependency conflict#environment setup#docker error#permission error

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 monthly subscription vs 5-hour/weekly limits: request for monthly bank or rollover [2 comments, 2 participants]