Two entry points cover the two things you actually care about: the CLI's /status command and the IDE extension status area show your own 5-hour/weekly windows; the radar shows the layer your machine can never see — how far the next global reset is.
The triage rule: wait 30–60 minutes and quota returns → the 5-hour window bit, just rest; still capped the next day → the weekly layer is binding, and usage frees up on the weekday it was spent.
One trap deserves its own warning: any third-party "usage tracker" asking for your ChatGPT credentials is a credential risk, not a feature — there is no official personal-quota API beyond the in-product displays. CLI/extension plus public archive tracking is the complete, legitimate answer.
FAQFAQ
Why doesn't /status match how it feels?
Because the limits are rolling windows, not a fixed pool: /status is a moment-in-time snapshot while your availability changes continuously as old usage slides out. Treat it as a status light, not a precise ledger.
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.