OpenAI Codex Pricing: Your Banked Rate Limit Resets Expire in 30 Days

OpenAI gave Codex users a feature that feels like a gift, then quietly attached a clock to it. Eligible Codex Plus and Pro users can now bank rate limit resets, but every banked reset expires 30 days after it is granted. For a heavy user who plans to save a reset for a busy week, that is not a bank. It is a short-dated coupon.

This matters far more than the headline suggests for anyone paying attention to OpenAI Codex pricing. Rate limits are the invisible tax of agentic coding. A reset is a get-out-of-jail card that lets you keep running Codex and ChatGPT Work when you would otherwise be cut off mid-task. Letting those resets silently age out changes what a subscription is really worth.

OpenAI Codex pricing and the reset 30 day clock

OpenAI’s June 11, 2026 release notes spelled out the deal. Eligible Plus and Pro users received rate limit reset banking, including one free reset at launch and referral invitations from inside the Codex app. When an eligible invitee sends a first Codex message, both people earn another banked reset.

The fine print is the hard part: banked resets are usable for 30 days after they are granted. The OpenAI Help Center now confirms that referral rewards granting a banked reset must be used within 30 days of being added to the bank, unless the offer says otherwise. A documented policy, yes. A well-surfaced one, no.

The complaints are public and ordinary, not edge cases. GitHub issue openai/codex#28888, opened June 18, asks OpenAI to extend the expiration window beyond 30 days. The reasons are everyday: vacation, travel, sick days, or a month where you simply do not need Codex heavily. That is exactly when a banked reset should help most. If it expires before the next burst of work, it never did its job.

The visibility problem makes it worse

The real friction is that users often cannot see when a reset will expire. The OpenAI Developer Community forum shows the mess. One July 13 thread described a Windows user who saw four banked resets on July 8, used one, then later saw only two remaining, with expiration dates of August 1 and August 12. Another July 2 thread captured simpler confusion: a user could see three resets but had no idea when each one expired, and an OpenAI Support reply did not give the full expiry picture.

That detail matters. Users are not just failing to read the fine print. In at least some places, the interface itself has not surfaced the full expiry timeline. GitHub issue #28805 asks for banked reset count, expiration, eligibility, and reset events anywhere Codex shows account usage. That is not a strange request. It is the minimum a developer needs to decide whether to burn a saved reset today or keep it for a deployment, a migration, or a long debugging session next week.

Two related issues round out the picture. Issue #28811 says a public reset appeared to be applied immediately instead of being banked. Issue #32586 proposes automatically redeeming an unused banked reset right before it expires, then notifying the user. Auto-redemption may not be the final answer, but silently letting resets lapse is a worse experience by any standard.

Why this hits heavy users hardest

Codex is growing into a compute management problem in public. OpenAI said in an April 2 product post that more than 2 million builders used Codex every week, while Codex use inside ChatGPT Business and Enterprise had grown six times since January. By July 21, Bloomberg reported OpenAI had reached 10 million users across Codex and ChatGPT Work, nearly double the level from earlier in the year.

More agents mean more long-running tasks, more token consumption, and more pressure on OpenAI to ration access without turning the whole product into a billing maze. That pressure is exactly why the expiration clock exists, and why it will keep tightening.

OpenAI has been moving the maze quickly. On April 2 the company moved Codex pricing toward token based usage per its Codex rate card, and introduced pay as you go Codex seats for teams. The same day it lowered annual ChatGPT Business pricing from $25 to $20 per user per month. A $100 monthly ChatGPT Pro add-on later gave heavier users more room, with a temporary usage bonus that also comes with conditions.

Every one of those changes touches the same nerve. Developers need to know what they can spend, when they will be cut off, and what happens when OpenAI gives them a reset. If the answer depends on an expiry clock buried somewhere else, the generosity starts to feel conditional in the worst way.

What to do as a heavy Codex user

If you run a team on Codex, treat the 30 day clock as the default until OpenAI changes it.

First, check your usage screen before assuming a saved reset will still be there next week. If your plan banks resets, log the grant date the moment one arrives and note the expiration. A spreadsheet or a reminder is enough. You now know a reset is only good for 30 days, so plan a heavy task into that window if you can.

Second, stop treating referral resets as permanent. They are the most likely to quietly lapse. If you are near the end of a 30 day window and have no heavy task on the calendar, burn the reset on a routine job rather than lose it.

Third, follow the open issues. The visibility and expiry mechanics are active complaints on openai/codex, and OpenAI has a history of tightening pricing and limits as demand grows. The policy that exists today (banked resets that expire on a quiet clock) may tighten further, not relax. Budget accordingly.

Codex is not a bad product. It is an unfinished one around the exact moment money and limits enter the room, and that is where unfinished details hurt most. If you are paying for a Pro tier or team seats, treat every banked reset as a perishable asset with a 30 day shelf life, and you will not find out the hard way that your balance was smaller than it looked.