When does Codex reset? Three different clocks

Five-hour usage windows and weekly limits

Official OpenAI documentation gives some plan usage estimates per five-hour period and notes that weekly limits may also apply. Those estimates are not a guaranteed number of messages. Model choice, task complexity, context, tool use and caching affect consumption.

Do not add five hours to a public announcement to calculate your next personal reset. More than one usage window can matter to your account. Read the actual window and recovery time displayed in your usage dashboard.

How to find your personal Codex reset time

1. Open the official Codex usage dashboard and confirm that you are using the same account and workspace as your current task.
2. Identify the exhausted window and read its displayed recovery time. A different window with remaining allowance may not resolve the one you have reached.
3. In an active Codex CLI session, use /status to check remaining limits and compare them with the dashboard.
4. If there is a new public reset announcement, read its plan scope and execution status. An announcement of future action is not proof that it has already happened.

How extra resets differ from normal recovery

An extra reset may be a one-off usage adjustment or a grant of a banked reset for later use. This site keeps regular and banked records separate and links to the underlying announcement. Eligibility can differ between announcements.

The large timer on the homepage measures time since the last confirmed reset. It is not time remaining until the next one. The average interval and longest wait summarize history; neither provides a fixed schedule.

UTC dates versus your local time zone

The heatmap groups announcements by UTC day, while displayed announcement times use your browser's time zone. A late-night UTC announcement can appear on the next calendar day in Asia. This is not necessarily a duplicate or an incorrect timestamp.

Compare the full timestamp and source link when checking a record. The API's announced_at field uses an ISO date-time value that applications can convert consistently.

Plan work around your account, not a prediction

Use your account usage display to plan work, with public history as context. Near a limit, consider a narrower task scope or whether the work needs its current model and context size. Do not rely on an unannounced extra reset arriving.

Browser notifications on the homepage can help you follow new public resets. The service checks every five minutes, but these are not personal account recovery reminders and delivery is not instantaneous or guaranteed.