Show 5-hour and weekly usage limits in the Codex App status area
What variant of Codex are you using?
Codex App (desktop)
What feature would you like to see?
Please show the current 5-hour usage limit and weekly usage limit persistently in the Codex App's bottom status/composer area, similar to the information available in Codex CLI.
A compact presentation would be sufficient, for example:
5h: 72% left · resets 14:30 | Weekly: 41% left · resets Jul 15
The indicator should:
- show both the 5-hour and weekly remaining usage;
- show their reset times;
- refresh automatically after usage changes;
- optionally open the full Usage view when clicked;
- optionally be hideable in Settings.
Why this would help
Usage limits affect whether a user should start or continue a long-running task. In the App, checking them currently requires leaving the active workflow and opening the Usage view. Meanwhile, the bottom status/composer area has substantial unused horizontal space, so it could display this operational information without crowding the conversation.
Codex CLI already demonstrates that these two limits can be presented compactly in a status line. Providing the same at-a-glance visibility in the desktop App would improve feature parity and make quota planning much easier.
Additional information
Related requests:
- #25561 asks for a persistent remaining-limit indicator in Codex Desktop.
- #30452 asks for easier access to usage limits during active App sessions.
This request is specifically for persistent, simultaneous display of both the 5-hour and weekly limits in the App's existing bottom status area, matching the useful at-a-glance behavior of Codex CLI.
Why the existing /status panel does not satisfy this request
Issue #24181 was closed as completed after usage information became available in the App. However, the current /status implementation is a different interaction from the persistent status indicator requested here:
/statusopens a large overlay that obscures a substantial part of the conversation.- The panel is temporary and may disappear, requiring the user to invoke
/statusagain. - It includes session and context details that are useful for an occasional inspection, but it is too large for continuous monitoring.
- Because checking it requires an explicit command and interrupts the current view, it does not provide at-a-glance quota awareness.
The requested indicator should instead:
- remain persistently visible in the otherwise underused bottom status/composer area;
- never cover the conversation or composer;
- show compact values for both the 5-hour and weekly/7-day limits and their reset times;
- update automatically and remain visible across normal thread activity;
- use a click or hover only for optional expanded details.
In short, /status should remain the detailed view, while the proposed status-line indicator should be the compact, always-visible summary.
Difference from the bot-suggested potential duplicates
The duplicate-detection bot referenced #31002 and #31027, but neither request is equivalent to this one:
- #31002 proposes a battery-style remaining-usage icon in the avatar bar. That would improve discoverability, but it does not explicitly provide an always-readable summary of both limit windows and both reset times in the existing bottom status area.
- #31027 asks for the large
/statuspanel to remain visible after switching sessions. Persisting that panel would fix its disappearance, but it would still leave a large overlay covering conversation content.
This issue requests a different UI treatment: a compact, non-modal, always-visible status-line summary. Fixing the /status panel's persistence alone should therefore not be considered completion of this request.
4 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
up
For Windows users following this request, I built an unofficial workaround that implements the same compact, always-visible idea inside Codex Desktop:
Codex Usage Monitor for Windows
https://github.com/JiaYang-BUAA/Codex-Desktop-Usage-Monitor-Windows
It adds an in-app status bar beside the composer for subscription quota/reset time, task token usage, API accounts, and API keys. The UI is injected at runtime through a localhost-only CDP connection; it does not patch
app.asaror modify WindowsApps. It uses a separateCodex Usage Monitorlauncher and is not affiliated with OpenAI.This is intended as a temporary, open-source Windows option. A native official indicator would still be preferable for reliability and update compatibility.
What variant of Codex are you using?
Codex desktop app on Windows.
What feature would you like to see?
Please add optional text-to-speech playback for Codex’s user-facing plans, progress updates, approval requests, errors, blockers, and final reports.
This should not expose private hidden chain-of-thought. It should read aloud the same user-facing operational summaries that Codex already displays or could reasonably generate for supervision.
Suggested playback options:
Why would this help?
Long coding and review sessions can require continuously watching the screen even when Codex is working independently. Spoken progress would reduce fatigue and make the workflow more accessible for users who prefer listening, have visual impairments, or need to monitor Codex while doing something else.
It would also improve supervision. Users could hear when Codex changes direction, encounters a blocker, requests authorization, launches subagents, or completes a milestone without staring continuously at the interface.
Important distinction
This proposal concerns spoken playback of Codex’s outgoing user-facing progress and results. It is not merely voice dictation, a completion sound, or access to hidden private reasoning.
This feature would make Codex more accessible and interactive while preserving a clear boundary between private model reasoning and auditable user-facing summaries.