The weekly limit is the longer Codex cap. Developers search this because the reset time is private — and because it can block you even after a 5-hour refresh.
/status. Third-party apps, including AI Limit, cannot read that private weekly clock.
OpenAI documents a weekly window that controls how much included work you can use over the weekly period. A shorter 5-hour limit may sit on top. Where both apply, remaining allowance is required in both.
On a light week you may only feel the 5-hour window. After several heavy days, the weekly cap is the one that stops a 5-hour reset from helping.
/status in an active Codex CLI session.There is no universal “Codex weekly reset time” in UTC. Community threads asking “how can I determine when it ends/resets?” exist because OpenAI does not publish one public clock.
| Weekly limit | 5-hour limit | |
|---|---|---|
| Question it answers | How much included work this week? | How much in this rolling window? |
| When it hurts | You are out until the weekly reset | You are paused mid-day |
| Can it block first? | Yes — 5-hour refresh will not help | Yes — even with weekly remaining |
If you're being blocked during a coding session rather than for the rest of the week, see our Codex 5-hour limit guide.
AI Limit
AI Limit tracks public Codex reset announcements. Confirm your private weekly timestamp in Settings or /status.
On the weekly timestamp in Settings / /status, unless a covered public reset or a redeemed full banked reset refreshes it.
Not without your OpenAI account. Codex usage tracker explains what AI Limit can and cannot see.
See Codex limit didn’t reset. Refresh the dashboard, confirm workspace, and check whether the 5-hour window is the one still at 0.
AI Limit monitors public Codex reset signals and sends an alert directly to your iPhone. It does not read your private ChatGPT / Codex remaining usage.
All Codex pages link back to the Codex Usage Limits & Reset Tracker hub.
Also see Claude Code, ChatGPT, and Cursor guides.