Include date in addition to time in Codex usage limits panel

Open 💬 3 comments Opened Jun 10, 2026 by gaf999

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

In the Codex usage limits panel, please keep the weekly refresh timestamp unambiguous when the reset is less than 24 hours away. Right now it can switch from a date like “Jun 11” to only a time like “6:41 PM,” which makes it unclear whether the reset is today or tomorrow.
Suggested formats:
Weekly reset: Jun 11, 6:41 PM
Weekly refreshes tomorrow at 6:41 PM
This would make quota timing easier to understand at a glance.

View original on GitHub ↗

3 Comments

etraut-openai contributor · 2 months ago

Which Codex product are you using? The TUI, IDE extension, app, or web version?

gaf999 · 2 months ago

Hello, I'm using the app, codex for desktop in windows

Gilberto A. Francisco
E-mail: @.**

A sexta, 12/06/2026, 07:01, Eric Traut @.***> escreveu:

etraut-openai left a comment (openai/codex#27435) <https://github.com/openai/codex/issues/27435#issuecomment-4687935725> Which Codex product are you using? The TUI, IDE extension, app, or web version? — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/27435?email_source=notifications&email_token=AVZGICBJ3JDVS3GZ6MHP2UL47OMD5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRYG44TGNJXGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4687935725>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVZGICENR2B7XHK7YPH5GPD47OMD5AVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TINRTGM4TOMRXHE42C5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AVZGICFSRK2GYE4BPPF5MZL47OMD5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRYG44TGNJXGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/AVZGICB6OOINEJFCHRPCPAT47OMD5A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTINRYG44TGNJXGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: @.***>

Drakokorian · 1 month ago

I am seeing the same UX ambiguity in the Codex app usage/reset display.

Observed wording:

Reset at 08:25

On Monday, July 6, 2026 in the Europe/Dublin timezone, that wording reads as if the reset should already have happened at 08:25 today, rather than clearly indicating the future weekly reset date. The display would be easier to understand if the weekly reset always included the calendar date and timezone, for example:

Resets Monday, July 13, 2026 at 08:25 Europe/Dublin

or a compact version such as:

Resets in 6 days • Mon, Jul 13 at 08:25 Europe/Dublin

This is especially helpful for weekly windows, where a time-only value can be interpreted as stale or broken once that time has already passed on the current local day.

I intended to attach a screenshot cropped to only the weekly reset row, but the current local capture did not have that row visible without exposing unrelated Codex workspace/thread content. Happy to provide a tightly cropped screenshot if maintainers need it.