Expose exact quota reset timestamps as status line items in Codex CLI.
Open 💬 2 comments Opened Apr 21, 2026 by zhw5592
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What variant of Codex are you using?
CLI
What feature would you like to see?
Example config:
```toml
tui.status_line = [
"model-with-reasoning",
"context-remaining",
"five-hour-limit",
"five-hour-limit-reset-at",
"weekly-limit",
"weekly-limit-reset-at",
"current-dir",
]
Expected behavior:
- render reset times in the user's local timezone
- update automatically as quota metadata changes
- render nothing when reset metadata is unavailable
- leave existing status line items unchanged
Additional information
This would make quota information in the status line much more actionable for planning work, especially when users are close to a 5-hour or weekly limit.
Existing related status line items include:
- model-with-reasoning
- context-remaining
- five-hour-limit
- weekly-limit
- current-dir
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
+1 on exposing reset info in the status line.
One suggestion on the format: in addition to absolute timestamps (e.g.
reset-at 14:32 local), a countdown form is often more actionable for in-flight planning decisions, e.g.:5h: 90% (3h 48m) | 7d: 93% (6d 14h)This is essentially what #17457 / #17456 proposed (closed for insufficient upvotes), and what users frequently reach for. Could this issue cover both presentations, or expose them as separate items, e.g.:
five-hour-limit-reset-at→ absolute timefive-hour-limit-reset-in→ countdownweekly-limit-reset-atweekly-limit-reset-inThat way users can pick whichever fits their workflow without each variant needing its own feature request.