Codex usage lives on two layers — your personal windows and the global reset rhythm — and each layer is checked in a different place. This guide walks through every reliable way to see where your quota stands, from the CLI to the radar.
Check your own quota: the /status command§
Inside the Codex CLI, type /status. It reports your session state and rate-limit information — the closest thing Codex has to a usage dashboard. Because the limits are rolling windows rather than fixed allowances, think of /status as a live snapshot rather than a ledger.
The same status surfaces in the IDE extensions (VS Code and friends): look near the agent panel for the rate-limit indicator. If it shows you're throttled, that's your answer — no hidden settings page needed.
Reading the two windows§
When you get throttled, you're hitting one of two ceilings: the 5-hour rolling window (short bursts) or the weekly window (total volume). The short one refills within hours; the weekly one frees up on the weekday the usage occurred.
A practical triage: wait 30-60 minutes and retry. If quota reappeared, it was the short window. If you're still capped the next day, the weekly layer is the binding constraint.
Check the global reset layer§
Your local tools can't see the most valuable layer: whether the team is about to refill everyone. That's tracked from official announcements on X, archived by codex-resets.com — 53 resets so far, averaging one every 6.9 days.
The live radar on this site turns that archive into a single number: reset pressure (days since last reset ÷ average gap), plus the latest official announcement when one is in flight. When a reset lands, every paid account's quota snaps back to full — the one usage check that doesn't need a dashboard.
What you can't (and shouldn't) check§
There's no supported way to read another account's usage, and no official API exposing your personal quota numbers beyond the in-product displays — third-party tools that ask for your ChatGPT credentials to "track usage" are a credential risk, not a feature.
Stick to first-party surfaces (CLI, IDE extension) and public trackers for the global layer. That combination covers everything the question "how much do I have left" can legitimately mean.
FAQFAQ
Is there a Codex usage dashboard on the web?
The authoritative in-product surfaces are the CLI /status command and the IDE extension status. There's no standalone web dashboard for personal Codex quota; global reset tracking is what public sites like this one provide.
How do I check usage from the terminal?
Run /status inside the Codex CLI. It prints session and rate-limit state for your account.
Does /status show exact numbers?
It shows your current window state; because limits are rolling and model-dependent, treat it as a status indicator rather than an exact token ledger.
How do I know when everyone gets refilled?
Watch the live radar: it tracks days since the last global reset against the 6.9-day historical average and flips to the exact time when an announcement lands.