Codex Usage Limits Explained: The 5-Hour Window, the Weekly Cap, and What Actually Resets (2026)

TL;DR: Codex Usage Limits Are a Window, Not a Count

The question "what are the Codex usage limits" has no single-number answer, and that is by design. OpenAI's pricing page, read today, describes an allowance that refills on a rolling five-hour window, varies by which model you run, may also be capped weekly, and is spent by tokens rather than by messages. Every ChatGPT plan gets a multiple of the same base allowance: Plus is the base, Pro 5x is five times it, Pro 20x is twenty times, and Business runs on the Pro 5x estimates. Nothing here is a fixed cap, which is why two people on the same plan report wildly different experiences. One runs Luna for quick edits and never sees the limit; the other keeps a 40-file repo in context on Sol and hits it before lunch.

I run Codex, Claude Code, and Cursor side by side on real client work, and the honest version of this post is that the limits stopped being the interesting question once I understood the meter. Here is the meter.

The Codex limits by plan, from OpenAI's own page (September 2026)

These are OpenAI's published estimates of local messages per five-hour period, and the page says out loud that they are estimates, not fixed message limits. Cloud chats run GPT-5.6 Sol by default and may consume more of the allowance than a local message does.

Three lines of fine print matter more than the table. Business ($20 per user per month billed annually, $25 monthly, two-user minimum) uses the Pro 5x estimates. "Weekly limits may also apply" is the page's exact phrasing, with no weekly number published. And "ChatGPT Work and Codex share usage", meaning agentic work you run inside ChatGPT draws down the same allowance as your CLI sessions. The Go tier ($8/month) exists for lightweight coding and is not in the estimate table; the API key route has no plan windows at all and bills at usage rates instead.

The 5-hour window: what resets and when

The window is rolling, not calendar-based. Usage you spent at 9am frees up at 2pm regardless of what you did in between, which is why a heavy morning and a heavy afternoon feel like two separate budgets and a heavy single stretch feels like a wall. The ChatGPT usage dashboard shows current limits and reset times; inside a Codex CLI session, /status shows the same thing without leaving the terminal. If you have never typed that command, type it before you decide you need a bigger plan.

The Codex weekly limit

OpenAI states that a weekly cap may apply on top of the five-hour allowance and does not publish it, which is the single most-searched frustration about this product and the reason "codex weekly limit" is its own query. What I can tell you from usage rather than documentation: on an ordinary week the five-hour window is the only limit you meet, and the weekly cap only becomes visible after several consecutive days of long agentic runs, at which point the five-hour reset stops helping. If you are hitting it, you are a heavy user by any definition, and the plan question below is a real one for you rather than a hypothetical.

Codex rate limits vs usage limits

The two phrases get used for the same thing, and the page itself mixes them. The rolling window and the weekly cap are what a ChatGPT-plan user means by either. The other meaning, rate limits in the API sense (requests and tokens per minute by API tier), only applies if you authenticate Codex with an API key instead of a ChatGPT login. That route drops the plan windows entirely, bills at API pricing, and gives up the cloud features (GitHub code review, Slack) that live on the ChatGPT side. It is the right choice for CI and shared environments and the wrong one for a person who wants a predictable monthly bill.

What burns the allowance faster than you think

• Context. A session holding a large codebase costs more per turn than a fresh one; the page lists context, reasoning, tool use, retrieval, and caching as the variables, and says prompt length alone is not a reliable estimate.
• Cloud chats. They run Sol by default and may use more of the allowance than local messages.
• Fast mode. Speed configurations consume credits at a higher rate and therefore use included limits faster.
• Images. Image generation draws on the same limits roughly three to five times faster on average.
• Voice. ChatGPT Voice on desktop has its own five-hour allowance (about 15–30 minutes on Plus, 1–2.5 hours on Pro 5x, unlimited on Pro 20x), but any Codex task started through Voice still draws from the Codex budget.
• Codex-Spark. GPT-5.3-Codex-Spark, the low-latency model in research preview for Pro, runs on separate hardware and a separate limit that can move with demand.

What happens when you hit the limit mid-task

The page is explicit that work in progress gets to finish: if you reach the limit during an active turn, the agent continues that turn subject to fair use. So a long migration does not die halfway; it stops accepting the next instruction. From there you have four moves, cheapest first: wait for the window, switch to a smaller model (Terra or Luna instead of Sol) so what remains lasts longer, buy additional credits (Plus and Pro can do this without changing plan), or run extra local chats against an API key at usage rates. Upgrading is the fourth option, and it is the one people reach for first.

Should you upgrade to Pro for the limits?

Decide it from the meter, not from a bad afternoon. Run /status at the end of three normal working days and note how often you were actually blocked versus annoyed. If Plus blocks you most days, Pro 5x at $100 is the honest tier, and it is worth knowing that OpenAI now sells that middle rung; the "$20 then $200 cliff" I described in my Codex pricing breakdown has a $100 step in it as of September 2026. If you are blocked once a week, buy credits and keep the $20 plan. If you are blocked because every session starts by re-explaining the whole codebase, fix the AGENTS.md and the task scoping first; how to use Codex covers both, and it is free. The same three-step order (threads, scoping, then money) is what I wrote for the Claude side in Claude usage limits, and the mechanism is identical.

The business-owner answer

If you own the company rather than write the code, here is the version I give on calls. A developer hitting Codex limits every day is either doing genuinely heavy work, in which case $100 a month is the cheapest engineer-hour you will ever buy, or is running the same kind of task by hand every morning, in which case the limit is a symptom and the fix is a workflow, not a plan tier. The AI Readiness Assessment ($2,500, credited in full against a build within 90 days) is how I tell those two apart in two weeks. And whatever tier you land on: before real users touch what Codex shipped, run it against the free 20-point vibe coding security checklist. Unreviewed agent output under a generous allowance is exactly how apps end up in my rescue queue.

Related: Codex pricing · is Codex free? · how to use Codex · Codex review · Cursor vs Claude Code vs Codex · Claude usage limits.