Extend banked Codex reset expiration beyond 30 days
What feature would you like to see?
Please extend the expiration window for banked Codex usage resets.
If banked resets currently expire after about 30 days, that window is too short for many users. A banked reset is most useful when it can cover occasional heavy workloads, vacations, travel, sick days, or periods where the user simply does not need Codex heavily that month.
A better policy would be one of:
- no expiration while the subscription remains active, or
- a much longer expiration window, such as 12 months, or
- at minimum, a grace window far longer than 30 days.
Why this matters
A 30-day expiration makes banked resets feel easy to lose accidentally. Users may receive a reset during a period when they cannot use Codex heavily, then lose it before the next real burst of work.
This weakens the main value of reset banking: smoothing uneven usage over time.
Expected behavior
Banked resets should remain available long enough for users to plan around them.
For example:
Banked resets: 1 available
Expires: Jun 18, 2027or, if no expiration is used:
Banked resets: 1 available
No expiration while subscription is activeRelated issues
- #28161 asks to show expiration dates for available resets.
- #28805 asks to show reset count, expiration, eligibility, and reset events in usage surfaces.
- This issue is specifically about the expiration policy itself being too short.
4 Comments
+1 on extending the window. The 30-day expiry is tight on its own, but it's compounded by the fact that the expiry date isn't surfaced anywhere (see #28161 and #29618). Right now resets can lapse silently — short window, no visibility. A longer window would give people a realistic chance to actually use them instead of losing them.
Related: #29618 is the assigned issue for exposing the expiry dates themselves.
At the very least, why not automatically apply it at the end of the window? I accidentally missed the window by 5 minutes and lost it. 30 days is one thing, but 30 days without an automatic redemption is rough, considering that there is a good amount of timing involved with when you should realistically spend it.
I also suggest to add exact timestamp to clarify time when expiration happen. Currently show date-only and make user panic to use bank reset ealier when it may have 10 hours left before it expired. Extend bank reset also save computation when user don't really need to burst usage. Entire customers force to burst within 30 days period may cause server overload. I also notice that reset recently don't add bank reset but reset immediately too. This is a problem because people may just use bank reset and got reset again from specific event/celebration.
Good news is the latest Codex desktop app shows the timestamp now! Would still love to see it auto apply if you don't use it in time...but to be fair, if they have implemented that I wouldn't know 😂. Miss one reset and you tend to be better about remembering the next time (even though Tibo tends to do a reset before I hit my natural limit anyways 🐐).