How to check Codex usage and remaining limits
Find your account allowance in Settings or the usage dashboard, inspect /status in an active CLI session, and use the /usage analytics dashboard in releases that support it.
Start here
Open the usage destination for your client and read the number there.
Documented places to look
The official guidance names these destinations. It does not guarantee identical menu labels across every client and version, so what follows describes where to go rather than what the button says.
Account-level
Settings or your usage dashboard. There you can check:
- which allowance is exhausted,
- your credit balance,
- any reset time shown.
Workspace members with credit-based billing have a more specific documented route: Settings > Usage & billing in the desktop app, which shows the monthly allowance and recent credit history.
Inside the CLI
/status in an active session. This is documented, and it is the fastest way to see your own state without leaving the terminal.
/usage is also documented in the Codex CLI 0.156.0 release notes: it opens an analytics dashboard for account usage, token totals, and plugin and skill activity. Use a release that supports this dashboard. These analytics are not interchangeable with every remaining-limit or reset-bank value.
An older reset-bank report is a separate observation
A user report on the public issue tracker shows the client printing:
• You have 3 usage limit resets available. Run /usage to use one.
This came from a report using CLI 0.144.1 on WSL. It does not establish what the newer analytics dashboard will display. The current OpenAI help article separately documents codex doctor for Windows diagnostics; it is not a usage-balance command.
Two things to be careful about:
- This reset-bank prompt is user-reported output. The newer documented
/usagedashboard is a different, version-scoped fact; do not assume the report describes its current behaviour. - The report itself was about reset counts apparently decreasing without use, and no maintainer confirmed a defect. Channel it into your expectations accordingly: if the number you see looks wrong, the correct conclusion is “worth checking”, not “the counter is broken”.
Why more than one number can be right
Different allowances can be in play at once:
- Plan allowance. Governed by your plan.
- Credits. A consumable balance; eligible users can buy more without changing plans.
- Workspace budget and user limit. On some workspace arrangements the administrator controls the effective user limit and reset period, so a number you see may be a policy value rather than a usage value.
- Shared pool. On plans that use a shared allowance, other features can consume from the same pool when they are available to you.
If you are looking at one number and behaving as though it were another, your reading will not match reality. Check which allowance is exhausted first.
API-key usage is a different screen
Plan-based usage and API-key usage are separate arrangements. Numbers from one do not describe the other. If your client is configured to use an API key, do not read plan allowances as the explanation for what you are seeing.
Quick checks
- Which client are you in? Use the route documented for it instead of assuming the desktop and CLI match.
- Does the number move when you work? If it does not change at all over a long session, you may be reading a summary rather than a live value.
- Have you changed plan, applied a reset or been granted one recently? Any of these can move the value legitimately.
- Are you comparing against someone else’s account? Limits vary by plan, so that comparison is not a test.
FAQ
Where can I check my remaining Codex allowance?
Open Settings or the Codex usage dashboard. In an active CLI session, use the documented /status command. Start with the view for the client and account you actually use.
Is OpenAI API usage the same as my Codex plan usage?
No. API-key billing and ChatGPT plan-based usage are separate arrangements. Match the usage view to the sign-in method before comparing balances.
Does Codex Rescue show my account balance?
No. This site points you to your account view. It cannot read your remaining allowance or infer it from public pricing or another user’s account.
Known limits of this guidance
- Evidence level: documentary for account-level routes,
/statusand the CLI 0.156.0/usagedashboard; the older reset-bank prompt remains reported only. - Menu labels and screen layouts differ by client and version, so no screenshots or exact label text are asserted.
- This guide does not state allowance amounts, because they vary by plan and change over time.
- If a displayed value looks wrong, the source material does not describe a self-service correction. The documented path for suspected incorrect usage is to contact support.
This guide is part of our Codex usage limits and reset guides.
Useful Codex tools
Sources
Each source lists what it is used to support. Sources are re-read on the review schedule, not continuously.
Using Codex with your ChatGPT plan (OpenAI Help Centre)
That when nearing or reaching a Codex limit the documented places to look are Settings or the usage dashboard, to check which allowance is exhausted, the credit balance and any reset time shown; that an active Codex CLI session accepts /status; and that members of eligible workspaces with credit-based billing can open Settings > Usage & billing in the desktop app to see the monthly allowance and recent credit history.
That a CLI message of the form 'You have N usage limit resets available. Run /usage to use one.' was observed in a user report, and that the same report's diagnostics came from a doctor-style command. Both are quoted as observed report output only - not as documented behaviour or as confirmed defects.
Codex CLI 0.156.0 release notes (2026-09-22)
The /usage analytics dashboard explores account usage, token totals, and plugin and skill activity in the 0.156.0 release. This does not establish that an older reset-bank prompt has identical behaviour.
Related guides
How this page is checked
- Evidence level
- Documentary - supported by official documentation
- Last reviewed
- 2026-09-28
- Content updated
- 2026-09-28
- Full version scope
- OpenAI account guidance read on 2026-09-28 and the CLI 0.156.0 release notes for the /usage analytics dashboard. The older reset-bank prompt was reported on CLI 0.144.1 in WSL; menu labels and command behaviour differ by release.
- Symptoms indexed
-
- You cannot find where the remaining allowance is shown
- You are not sure whether a number you found is the current one
- You want to know which of your allowances is exhausted
Reviewer note
Official account guidance, the 0.156.0 release entry and the original issue were reopened on 2026-09-28. The former report-only description of /usage was corrected to reflect its documented analytics dashboard; the older reset-bank output remains a version-specific report, not a confirmed defect or current command contract. FAQ and related links added on 2026-09-28; the full-article review date remains as shown.