CODEX RESET RADAR Codex Reset Radar
中文
CODEX BASICS · TOPIC

Usage tracking: what's left and where to look

Two first-party surfaces answer personal-usage questions: the Usage Dashboard shows exact limits and reset times, while CLI /status shows remaining limits. The radar is separate and only tracks public announcements.

Read both allowance indicators, copy the reset time shown by the account, then compare any public event. Do not infer an undocumented formula from a 30-minute wait or last week's activity.

Any third-party tracker asking for ChatGPT credentials is a risk. The timer on this site only accepts a date you enter manually and keeps it in your browser.

FAQFAQ

Why doesn't /status match how it feels?

/status is a remaining-limit snapshot, while actual consumption varies with model, task, context, reasoning and tool use. Use the Usage Dashboard for the exact reset time.

Can I check someone else's usage?

No, and there's no legitimate path to it. Officially there's no cross-account usage data; tools claiming otherwise are the risk.

The radar and my account disagree — which is right?

They track different layers: the radar watches the global-reset layer (official announcements), your account shows personal windows. Personal quota is /status's job; the global layer belongs to announcements and the radar.

🎯 Any confirmed public reset today?
Open the signal radar for sourced announcements; personal allowance and exact reset time remain in Usage.
Open the signal radar →