Show expiration dates for each available usage reset

Open 💬 8 comments Opened Jun 14, 2026 by GGBondBlueWhale

Codex app version

Desktop Codex: 26.609.41114 — released Jun 12, 2026

Platform / plan

  • macOS Tahoe 26.5.1
  • Pro plan

Summary

Please show the expiration time for each available usage reset.

In the account menu, Codex currently shows something like:

2 resets available

However, if reset opportunities expire after a limited time window, for example around 30 days, the UI should show the remaining expiration time for each reset.

Current behavior

The menu only shows how many resets are available, but it does not clearly show when each reset will expire.

This makes it hard for users to know whether they should use a reset soon or whether it is safe to save it for later.

Expected behavior

Codex should display the expiration date or remaining time for each available reset, such as:

  • Reset 1: expires in 12 days
  • Reset 2: expires in 27 days

or:

  • Reset available until Jun 25
  • Reset available until Jul 8

Why this matters

If resets have an expiration window, users need to know when they will expire. Otherwise, users may accidentally lose reset opportunities simply because the UI did not warn them in advance.

Showing the expiration time would help users plan their usage more reasonably and use resets before they expire.

Request

Please add an expiration date / countdown display for each available reset, and consider showing a warning when a reset is close to expiring.

View original on GitHub ↗

8 Comments

furkancak1r · 1 month ago

Adding another current report from Windows Codex Desktop:

  • Codex Desktop: 26.611.61753 (released 17 Jun 2026)
  • Platform: Windows

Same concern: banked usage resets appear to be time-limited, around 30 days, but the UI does not show the exact expiration date/time or remaining countdown. Without that, users cannot tell whether a reset is safe to save or needs to be used soon.

The minimum useful UI would be enough, for example:

  • 1 reset available
  • Expires Jul 18, 2026 or Expires in 12 days

This should be visible wherever Codex shows reset/usage state. Related broader tracking issue: #28805.

coygeek · 1 month ago

See my workaround on #28963

myudak · 1 month ago

literally why is this not a thing

scyuo · 22 days ago

I can reproduce this on Codex CLI 0.142.3 on macOS Apple Silicon.

/usage shows:

  • Show usage
  • Redeem usage limit reset
  • You have 2 usage limit resets available

But Show usage only opens token activity views (daily, weekly, cumulative) and does not show the expiration date/time for available reset credits.

The only visible reset-related path is Redeem usage limit reset, which feels unsafe as a discovery path because users cannot tell whether they are only viewing reset state or about to consume a reset.

It would be helpful if /usage exposed reset credit state in a read-only way, for example:

  • available reset count
  • next expiration date/time
  • days remaining
  • whether selecting the reset flow is view-only or destructive

This matters because the UI says the reset opportunity expires after about 30 days, but there is no exact date available for setting a reminder before expiration.

Lisenish · 21 days ago

There's a workaround for that, I think expirations are even in API response, they're just not visible in UI. Ask your agent to figure out API how to get an API response and show them to you

vtsixthai · 14 days ago
Adding my voice here. The single most useful thing for me would be seeing the latest use-by date across my whole bank — i.e. the date by which I need to have used my resets. Right now I see "X resets available" with no date, so I can't tell whether I should use one today or safely hold onto them. A single "use your resets by <date>" line would fix most of the problem for me; per-reset expiry would be even better.
ryanbliss · 3 days ago

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.

Alternatively, just always have it reset at 11:59 PM in the user's timezone (from the user's timezone that was configured when the reset was added, to avoid misuse).

krazykoder · 3 days ago

me too i missedmy reset - i did not know what time it was expiring at PST timezone.