Codex App /status menu does nothing or no longer shows remaining usage limits
Summary
In the Codex desktop app, opening the slash command menu with / and selecting Status currently appears to fail: the status panel does not open, or it no longer shows the remaining usage/rate-limit information users expect.
Please fix this regression. The remaining usage limits are important during active Codex sessions, especially for long-running work.
Environment
- Product: Codex desktop app
- Platform: Windows
- Date observed: 2026-05-28
- Slash command:
/status/ Status from slash menu
Expected behavior
Selecting Status should open the status view and show useful session/rate-limit information, including remaining usage limits or a clear link/path to the Codex usage dashboard.
Official documentation still says current limits are available in the Codex usage dashboard and that /status can be used during an active Codex CLI session to see remaining limits:
https://developers.openai.com/codex/pricing#where-can-i-see-my-current-usage-limits
The IDE slash-command documentation also describes /status as showing thread ID, context usage, and rate limits:
https://developers.openai.com/codex/ide/slash-commands#available-slash-commands
Actual behavior
- Typing
/and clicking Status in the Codex app does not reliably open the expected status view. - Remaining usage/rate-limit information is not visible from the Codex app where the work is happening.
- Users have to leave the app and manually check
https://chatgpt.com/codex/settings/usageinstead.
Related context
This appears related to prior requests/regressions around making remaining usage visible in the Codex app UI, for example #19869. If the current behavior is intentional, please document where users should check the five-hour and weekly limits from inside the app.
2 Comments
yes please fix this! first it stopped working in vscode extension, now in the codex app? almost feels like youre supposed to stop caring about limits and just upgrade to a higher plan...
I am experiencing the same issue with the WEB interface, which completele conceals the fact that work-labeled chats consume paid quota tokens, and have also created a separate post about it here:
Stop Hiding Weekly Usage: ChatGPT Work Now Drains the Codex Quota Without Warning
The lack of a clear, persistent usage indicator—combined with the poorly explained shared quota between Codex and ChatGPT Work—is causing unnecessary confusion for paying users.
I am linking the discussions so the reports can be cross-referenced and the broader impact of this issue is easier to see.