Repository navigation
Codex IDE Usage Request #44966
Description
What variant of Codex are you using?
IDE Extension (Visual Studio)
What feature would you like to see?
Codex usage limits are too difficult to understand and too easy to hit unexpectedly. I want a straightforward, always-visible indicator showing how much usage I have left in my current 5-hour window and weekly allowance, ideally with an estimate based on my selected model and effort level. Most importantly, Codex should warn me before starting a task if I’m close enough to the limit that the task may be interrupted. Getting a “usage limit reached until 2:43 AM” message while Codex is already processing a prompt is a poor experience, especially when working on an active coding project. Model and effort choices affecting consumption should also be explained clearly in the UI.
Additional information
No response
Activity
github-actions commentedon Sep 12, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
rozziesquare commentedon Sep 23, 2026
Two related suggestions:
First, please keep the current 5-hour and weekly usage numbers permanently visible in the Codex panel in VS Code, perhaps in a small fixed area at the bottom. For Plus and other non-Pro users, remaining usage is important enough that it should not require opening another control such as “Work locally.” Ideally, the panel would always show the current 5-hour and weekly remaining usage/reset information, with a detailed view available separately.
Second, please consider a small, bounded usage “grace” allowance for work already in progress. If Codex reaches the limit while actively carrying out a request, it could finish that current action instead of stopping abruptly, with the small overage automatically deducted from the next usage allocation after reset.
This grace should not allow starting new work after the limit is reached; it would only let already-started work finish. Any borrowed amount should be clearly shown in the usage UI.
Together, these changes would make limits easier to manage: one helps users avoid hitting them unexpectedly, and the other prevents an active task from being interrupted at an awkward point.