Where to actually check your Codex usage

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.

Reported but not documented here

A user report on the public issue tracker shows the client printing:

• You have 3 usage limit resets available. Run /usage to use one.

and the diagnostics in that same report came from a doctor-style command.

Two things to be careful about:

• These appear in user-reported output, not in the documentation this guide is built on. Commands can change between versions, and this site does not present them as documented 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

1. Which client are you in? Use the route documented for it instead of assuming the desktop and CLI match.
2. 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.
3. Have you changed plan, applied a reset or been granted one recently? Any of these can move the value legitimately.
4. Are you comparing against someone else’s account? Limits vary by plan, so that comparison is not a test.

Known limits of this guidance

• Evidence level: documentary for the account-level routes and /status; the /usage command and the doctor-style diagnostic are 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.