Codex Reset Radar
🌐 English

How to check Codex usage: /status, /usage, and the usage dashboard

The three places Codex usage actually shows up — the /status limit bars, the /usage menu, and the web usage dashboard — how to read them, and the display bugs that make the numbers disagree.

Short answer: Type /status inside a Codex session for your two limit bars and their reset times, /usage for token activity and reset redemption, or open the web usage dashboard for the authoritative account-level view. When they disagree, the dashboard wins.

This is an unofficial tracker. It is not affiliated with OpenAI. Codex is a product/trademark of OpenAI. Probability scores are public-signal heuristics, not authoritative announcements or certainty.

Three places, three jobs

/status (typed at the Codex prompt inside a running session, not codex /status in the shell) prints a box with your model, session, and two limit bars. /usage opens the account-level menu: token activity (daily / weekly / cumulative) and, if you hold one, redeeming a banked reset. The web dashboard at chatgpt.com/codex/settings/usage is the account-level view OpenAI points to for current limits and reset times. OpenAI's pricing page describes /status as the way to "see your remaining limits during an active Codex CLI session"; the CLI command reference describes it as "Display session configuration and token usage".

Reading the /status bars

The /status box prints one bar per window, in the shape captured in openai/codex #29948: 5h limit: [██░░] 82% left (resets 22:41) and Weekly limit: [███░] 97% left (resets 17:41 on 1 Jul). Three reading rules. First, "resets" times are your own window clocks — not a platform-wide reset, and not something any tracker can see. Second, the clock timezone is not documented; when in doubt cross-check the dashboard. Third, the weekly line carries a date, the 5h line usually just a time (the maintainers confirmed day-shown-if-not-today in #5115).

What /usage is for

The /usage menu is where token activity lives — the daily heatmap, weekly bars, and cumulative totals — and it is also where an earned or banked reset is redeemed. Keep the two commands straight: /status answers "how much window do I have left and when does it refill", /usage answers "where did my tokens go, and do I want to spend a reset now". If /usage reports a sign-in requirement, the session lacks Codex service-account auth. If a redeem fails there with "Couldn't reset usage", read our dedicated page for that error before clicking again.

When the numbers disagree

They sometimes do, through no fault of yours. The bars can be stale on first run — the CLI itself warns "limits may be stale - run /status again shortly", and #4761 documented reset timestamps offset after session resume (fixed since). Worse, #29948 captured a session blocked with "You've hit your usage limit" while the bars still showed 82%/97% left — a state OpenAI labelled bug/rate-limits. The standing rule: when the CLI and the server disagree, the server's answer (the dashboard) is the one that counts. For the fuller pattern of "signal said reset, my UI didn't move", see why your Codex limit didn't reset.

Two clocks, one decision

The two bars are two separate windows — the short 5-hour window and the weekly quota — and they refill independently. You can hit the 5-hour wall with weekly allowance left, or drain the weekly quota while a fresh 5-hour window means nothing. Before scheduling deep work, read both bars and trust the smaller one for "can I start now" and the weekly one for "can I finish". Our 5-hour vs weekly limit explainer covers the full decision table, and what a Codex usage limit reset covers explains what a reset actually refills.

Put your "resets HH:MM" against the public timeline

The times you just read from /status are yours alone — but one useful cross-check exists: if your window refill lands close to a public reset event, other users' reports cluster around the same moment. The radar below shows the latest public signal. If your /status clock and the public timeline match, you are simply riding the same wave as everyone else; if they diverge, your clock governs.

Latest public signal (radar snapshot)

Latest public signal: Tibo on X: banked reset activated — lands in everyone's accounts soon (Nov 12) (2026-11-12) · Public signals logged: 64

Radar monitor

Last radar sweep: 2026-11-22 15:15 UTC. The radar logs public signals only. It cannot see your /status output, your windows, or your quota — by design.

Your /status bars and the usage dashboard are authoritative for your account. The radar adds platform-level context only. See the live radar →

Reading order for a heavy run

One: /status — both bars, both reset times. Two: if the 5h bar is low but weekly is healthy, either wait out the short window or start lighter work. Three: if weekly is low, that governs — check when the weekly limit resets before committing to a long task. Four: only then consider a banked reset, using the decision table in should you use a banked reset.

Sources: real output and real bugs

The /status bar format on this page is quoted from openai/codex #29948 (also the source of the bars-vs-block mismatch). Reset-time display rules: #5115. Stale/offset reset timestamps after session resume: #4761. Command descriptions: OpenAI Codex CLI command reference and pricing page. Usage dashboard URL and reset mechanics: OpenAI Help Center, "How resets work in Codex". These are community/public reports and official docs, quoted for accuracy — not claims by this tracker.

Want the next strong Codex reset signal?

Get an email when the radar logs a stronger public reset signal.

Get reset alerts →

How to check Codex usage: /status, /usage, and the usage dashboard FAQ

Do I type /status in the shell or in Codex?

In Codex. /status is a slash command typed at the prompt inside a running Codex session. Typing codex /status in your shell is a different thing and won't print the usage box.

What does "resets 22:41" mean in /status output?

It is the clock time your own 5-hour window refills — a personal window clock, not a platform-wide reset. The weekly bar works the same way, with a date attached. No third-party tracker can see these; they come from your session.

Why does /status show quota left but Codex still blocks me?

That exact mismatch is a documented bug: #29948 captured "You've hit your usage limit" with 82%/97% left on the bars. When CLI display and server state disagree, trust the web dashboard, and report the mismatch with your /status box attached.

/status or /usage — which one should I check?

/status for "how much do I have left and when does it refill"; /usage for "where did my tokens go" and for redeeming a banked reset. They answer different questions; heavy users end up using both.

Is there an API to check my Codex usage?

OpenAI has not shipped a public personal-quota API. The surfaces are the CLI commands and the usage dashboard. Any third-party tool claiming to read your personal quota is either using your credentials (avoid) or guessing (also avoid).

How often should I check?

Before every heavy run. Reading two bars takes ten seconds and prevents the classic failure: starting a long refactor with 3% weekly left. Set an alert for public reset signals if you plan around them — that is what our reset alerts are for.

Related Codex reset guides