Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Expose exact quota reset timestamps as status line items in Codex CLI. [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18812•Fetched 2026-04-22 07:52:18
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
0
Author
zhw5592zhw5592
Participants
github-actions[bot]github-actions[bot]zhw5592zhw5592
Timeline (top)
labeled ×5unlabeled ×2commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI

What feature would you like to see?

Example config:

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

extent analysis

TL;DR

To improve the quota information display in the status line, consider modifying the tui.status_line configuration to include timezone-aware reset times and dynamic updates based on quota metadata changes.

Guidance

  • Review the existing tui.status_line configuration to ensure it includes all necessary items, such as five-hour-limit-reset-at and weekly-limit-reset-at, which seem to be related to the desired functionality.
  • Investigate the possibility of using a timezone-aware formatting option for the reset times, if available in the Codex CLI.
  • Consider adding a feature request or issue to the Codex project to support automatic updates of quota metadata in the status line, if this is not already implemented.
  • Verify that the existing status line items, such as model-with-reasoning and context-remaining, are not affected by the proposed changes.

Example

No code snippet is provided, as the issue does not contain sufficient technical details to create a specific example.

Notes

The proposed solution assumes that the Codex CLI provides some level of customization for the tui.status_line configuration and that the desired functionality is not already implemented.

Recommendation

Apply workaround: Modify the tui.status_line configuration to include timezone-aware reset times and investigate possibilities for dynamic updates, as this seems to be the most feasible approach given the provided information.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#docker error#permission error#memory optimization#batch processing#GPU compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING