Personal usage windows
Your five-hour and weekly limits belong to your account and workload. Use the reset time shown in Settings → Usage; another person's countdown may not match yours.
Turn the reset time shown by Codex into a clear local countdown, then understand what each usage window means.
Your five-hour and weekly limits belong to your account and workload. Use the reset time shown in Settings → Usage; another person's countdown may not match yours.
OpenAI may announce a broader reset or temporary allowance for many users. Treat that as a separate event, not a prediction of your normal account window.
Eight quick questions about five-hour windows, weekly limits, and banked resets. No login, no tracking—just bragging rights.
Take the reset quiz →Public announcements for many users, kept separate from your personal account window. This does not predict the next reset.
Public records use WhenReset's open feed and link to original sources. Your browser requests that public feed without including timer entries; historical averages only describe the past.
One search question, one focused answer—grounded in current public OpenAI guidance and honest about account-specific limits.
A practical guide to the shorter Codex allowance: how the window starts, where to find its reset time, why usage varies, and what to do when it runs out.
Read guide →LONG WINDOWUnderstand the weekly Codex allowance, its relationship to the five-hour window, and the important differences between automatic, banked, purchased, and credit-based options.
Read guide →TIME CHECKUse the time shown in your own Usage screen, then convert it into a clear local countdown.
Read guide →TROUBLESHOOTA short diagnostic path for unexpected limits, missing credits, and reset times that appear not to update.
Read guide →Advertising supports this independent guide. Google AdSense is connected and any displayed ad remains clearly labelled.
The calculator runs in your browser. We do not ask for an OpenAI login, API key, usage screenshot, or payment information.
Read the FAQ →