Usage limit retry message shows stale past date after reset time passes

What version of the Codex App are you using (From “About Codex” dialog)?

26.810.52044

What subscription do you have?

Usage limit retry message shows stale past date after reset time passes

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

Usage limit retry message shows stale past date after reset time passes

Description

When a usage limit is hit, the error message includes a retry timestamp (e.g., "try again at Aug 20, 2026, 7:38 AM"). After that date passes, the message updates to show the new reset date instead of indicating the limit was already reset.

Impact

Confusing UX, the user sees a usage limit error with a future date even though their limit has already reset. This may prevent users from retrying when they should be able to.

What steps can reproduce the bug?

Steps to Reproduce

1. Hit the usage limit and message shows: "You've hit your usage limit... or try again at Aug 20, 2026, 7:38 AM"
2. Wait until after Aug 20 (e.g., Aug 27)
3. The message now shows: "You've hit your usage limit... or try again at Aug 27, 2026, 7:38 AM"

Actual Behavior

The message updates to show a new future reset date, which is misleading since the user's usage has already been reset and they have 100% usage remaining.

What is the expected behavior?

The message should either:

• Stay the same (showing the original reset date)
• Indicate that the limit has already been reset (e.g., "Your limit has already been reset.")

Additional information

I would like to open PR https://github.com/openai/codex/compare/main...jramosg:fix/usage-limit-reset-message?expand=1

No source file or test is named. Start by locating the usage-limit retry message entry point and reproduce the behavior across the reset time; done means the message no longer presents a misleading future retry date after the limit has reset.