codex - 💡(How to fix) Fix Add a built-in status-line item with reset countdowns [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#17456Fetched 2026-04-12 13:28:29
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×4closed ×1commented ×1cross-referenced ×1

Please consider adding a new built-in TUI status-line item, quota-summary, that renders the 5-hour and weekly quota remaining percentages together with reset countdowns.

Example output:

5h:87%(2h1m) wk:50%(5d22h)

Root Cause

Please consider adding a new built-in TUI status-line item, quota-summary, that renders the 5-hour and weekly quota remaining percentages together with reset countdowns.

Example output:

5h:87%(2h1m) wk:50%(5d22h)

Fix Action

Fix / Workaround

For users who rely on Codex for scheduling and dispatch decisions, the reset countdown is the important missing piece. Remaining percentage alone is not enough to decide whether it is safe to start a high-throughput or long-running task.

  • deciding whether to dispatch a coordinated team workflow
  • deciding whether to start a long-running debugging/refactor session
  • reducing unnecessary context switching to other tools just to inspect reset windows

If this direction is aligned with the team’s intended solution, I already have a working branch and can provide details or a patch outline in the issue discussion.

RAW_BUFFERClick to expand / collapse

Title: Add a quota-summary built-in status-line item with reset countdowns

Summary

Please consider adding a new built-in TUI status-line item, quota-summary, that renders the 5-hour and weekly quota remaining percentages together with reset countdowns.

Example output:

5h:87%(2h1m) wk:50%(5d22h)

Problem

The existing built-in limit items expose remaining percentages, but not the countdown-to-reset signal.

For users who rely on Codex for scheduling and dispatch decisions, the reset countdown is the important missing piece. Remaining percentage alone is not enough to decide whether it is safe to start a high-throughput or long-running task.

This matters especially for:

  • deciding whether to dispatch a coordinated team workflow
  • deciding whether to start a long-running debugging/refactor session
  • reducing unnecessary context switching to other tools just to inspect reset windows

Proposed Design

Add a new built-in status-line item:

  • quota-summary

Behavior:

  • additive only; do not change existing five-hour-limit or weekly-limit semantics
  • render short-form quota remaining plus reset countdown
  • omit unavailable windows instead of rendering placeholders

Suggested format:

  • 5h:87%(2h1m) wk:50%(5d22h)

This keeps the current status-line architecture intact:

  • one new built-in item
  • one shared formatter for quota-summary display
  • existing items remain backward-compatible

Why This Shape

I am not asking for a full custom multi-line HUD or a Claude-style footer clone here.

A single additive built-in item is much lower risk:

  • no change to existing item semantics
  • small surface area for maintenance
  • easy to document and test
  • useful immediately for scheduling decisions

Notes on Scope

This proposal intentionally does not require:

  • arbitrary custom footer rendering
  • multi-line footer layout
  • custom progress-bar glyph rendering

Those are larger UI/design questions. This request is specifically about exposing the reset countdown signal in the existing status-line system.

Verification from a Local Prototype

I implemented this locally as an additive quota-summary item in the TUI and verified:

  • config/setup picker support
  • runtime status-line rendering
  • countdown formatting from existing rate-limit reset timestamps

Targeted verification used:

cargo test -p codex-tui --lib quota_summary -- --nocapture

Why It Seems Aligned

The existing status-line system already has:

  • a fixed built-in item enum
  • rate-limit data in TUI state
  • existing 5-hour and weekly limit items

So this seems like a natural additive extension rather than a new subsystem.

If this direction is aligned with the team’s intended solution, I already have a working branch and can provide details or a patch outline in the issue discussion.

extent analysis

TL;DR

Implement a new built-in TUI status-line item, quota-summary, to display the 5-hour and weekly quota remaining percentages along with reset countdowns.

Guidance

  • Review the proposed design for the quota-summary item to ensure it aligns with the existing status-line architecture and does not introduce any backward compatibility issues.
  • Verify that the implementation of the quota-summary item does not require any changes to the existing five-hour-limit or weekly-limit semantics.
  • Test the quota-summary item with different quota remaining percentages and reset countdowns to ensure it renders correctly in various scenarios.
  • Consider adding documentation for the new quota-summary item to help users understand its behavior and usage.

Example

No code snippet is provided as the issue does not contain any specific code examples.

Notes

The implementation of the quota-summary item seems to be a low-risk additive change, but it's essential to review and test it thoroughly to ensure it does not introduce any unintended consequences.

Recommendation

Apply workaround: Implement the proposed quota-summary item as described in the issue, as it seems to be a natural extension of the existing status-line system and aligns with the team's intended solution.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Add a built-in status-line item with reset countdowns [1 comments, 2 participants]