Codex usage limits: how to check what's left and when it resets

Codex stops mid-task with a usage limit message, and you want to know two things: how much is left, and when it comes back. Here's how the limits work on each ChatGPT plan, where to check them, and what to do when you run out.

Watch Codex from your notchNotchDodo, $9.99 one-time
The short answerWhen you use Codex with a ChatGPT sign-in, usage comes out of your plan's allowance. On Plus and Standard Business that's a 5-hour window plus a weekly window; Pro currently has only the weekly one. To see what's left, type /status in the Codex CLI or open chatgpt.com/codex/settings/usage. The 5-hour window resets five hours after the first message that opened it, and the weekly window seven days after the week began. When you run out, wait, use credits, or switch Codex to an API key. Figures here are from OpenAI's docs as of 13 November 2026 and change often.

How Codex usage limits work

Codex can bill you in two different ways, and the limits only apply to one of them.

  • Signed in with ChatGPT. Codex uses the allowance included in your ChatGPT plan. This is where usage limits, the 5-hour window and the weekly window come in. Codex in the CLI, the IDE extension, the desktop app and Codex cloud all draw from it.
  • Signed in with an API key. You pay per token at API rates, with no plan allowance to run out. OpenAI notes that cloud features such as GitHub code review and the Slack integration aren't included this way, and the models you can pick follow what your key has access to.

On plans with both windows, they run side by side. The 5-hour window caps short bursts of heavy work; the weekly window caps your total for the week. Running out of either one stops new work until it resets. OpenAI's help center also points out that you can hit the 5-hour limit before five hours have passed, even with weekly usage left.

Diagram of two Codex usage windows: a 5-hour window that opens at the first message, 9:10 to 14:10, a gap, then a second window from 16:30 to 21:30, and a weekly window that resets seven days after it starts
The 5-hour window opens with your first message and closes five hours later. The weekly window runs alongside it. Example times.

Local and cloud work share the same pool. In OpenAI's words, local messages and cloud chats share your plan's usage allowance, and cloud tasks may use more of it than local messages.

Codex limits by ChatGPT plan

This is how OpenAI describes each plan in its Codex pricing page and help center as of November 2026:

Plan5-hour windowWeekly windowWhen you run out
Free and GoCodex for quick or lightweight tasks; no numbers published. No Codex cloud.Wait, or use an API key; credits only for some accounts
Plus ($20/month)YesYesCredits, a paid reset where offered, or an API key
Pro ($100, $200 or $500/month)None at the momentYesCredits, a paid reset where offered, or an API key
Business, Standard seatYes, same limits as PlusYesWorkspace credits, if your admin allows
Enterprise and Edu, flexible pricingNo fixed rate limits; usage scales with workspace creditsWorkspace credits
Enterprise and Edu, no flexible pricingRoughly the same per-seat limits as Plus for most featuresAsk your admin

Two things to know about that table. First, it moves: OpenAI removed the 5-hour window for Plus in July 2026 and brought it back on 25 August 2026, saying it would keep the 5-hour limit off for Pro "for the upcoming months". Second, ChatGPT Business also has Premium seats, which OpenAI says include more usage than Standard seats and aren't subject to a 5-hour limit.

How many messages do you get?

OpenAI doesn't give a single number, because a "message" can be a one-line fix or an hour of agent work. Instead it publishes estimated ranges of local messages per 5-hour window for Plus and Standard Business. As of November 2026:

ModelLocal messages per 5 hours (estimate)
GPT-6 Astra5 to 45
GPT-6 Sol15 to 150
GPT-6.1 Sol15 to 160
GPT-6.1 Terra35 to 285
GPT-6 Luna350 to 3,000

OpenAI is clear that these are estimates, not fixed limits: where you land depends on the model, how big the task is, how much context it carries, reasoning effort, tool use and caching. Speed modes matter too. Per the same page, Fast mode uses included usage 2.5 times as fast as Standard, and Ultrafast on GPT-6 Astra and GPT-6.1 Sol uses it 8 times as fast. OpenAI doesn't publish matching ranges for Pro or for cloud tasks.

How to check your Codex usage

In the Codex CLI: /status

Type /status in any Codex session. OpenAI's docs say it displays the session configuration and token usage (active model, approval policy, writable roots and how much context is left), and the pricing page says it's how you see your remaining limits during an active CLI session. If it doesn't show limits yet, send a message first so the session has talked to your account.

Illustrative mock of a Terminal running Codex, showing /status output with model, approval policy, writable roots, context, and bars for the 5-hour and weekly limits
Illustrative mock, not real output. The exact layout of /status varies by Codex version and plan.

In the Codex CLI: /usage

/usage opens a usage menu. From there you can view your ChatGPT token activity or redeem a rate-limit reset you've earned. You can also jump straight to a view:

Codex
/usage            # opens the usage menu
/usage daily      # token activity by day
/usage weekly     # token activity by week
/usage cumulative # total token activity

If you'd rather not type a command, the CLI's status line can show rate limits along the bottom of the screen; OpenAI's slash command docs list rate limits as one of the items you can put there.

On the web: the Codex usage dashboard

  1. Open chatgpt.com/codex/settings/usage while signed in to the same ChatGPT account Codex uses.
  2. Look at what's left in each window and when it resets.
  3. Check it every week or two, as OpenAI suggests, to get a feel for your pace before you hit a wall.

The Codex desktop app also has Usage settings, which is where eligible accounts can buy a reset.

When does the Codex limit reset?

  • The 5-hour window doesn't run on clock hours. A new window starts when you send your first Codex or ChatGPT Work message after the previous one has ended, and lasts five hours from there. So if your first message is at 9:10, that window ends at 14:10; if you then don't touch Codex until 16:30, the next window runs 16:30 to 21:30.
  • The weekly window resets seven days after your weekly period started. Your dashboard shows the exact date.
  • Early resets. OpenAI occasionally resets limits for free, and some promotions and referral offers give you a banked reset you can use later from /usage. A full banked reset refreshes both windows; used when only the 5-hour window is spent, it can restore that one without restarting your week.

What happens when you hit the Codex limit

If you run out in the middle of a turn, OpenAI says the agent can keep working on that turn, subject to fair use limits. New work stops after that. Your options, roughly from cheapest:

  1. Wait for the reset. Check the time with /status or the dashboard.
  2. Use credits. Your plan's included usage is used first; after that, Codex can draw from a ChatGPT credit balance so you keep working without changing plans. Plus and Pro users can buy credits; Business, Edu and Enterprise workspaces on flexible pricing buy workspace credits.
  3. Buy an instant reset. Eligible personal Plus and Pro accounts can buy one on ChatGPT web or the Codex desktop app, from Usage settings or the weekly-limit banner. It restores both the 5-hour and weekly allowances immediately, can't be saved for later, and starts a new weekly period with your next request. It isn't offered on Free, Go, Business, Enterprise or Edu, and OpenAI generally doesn't refund it.
  4. Switch to an API key. OpenAI says anyone can run extra local chats with an API key, charged at standard API rates. Sign in with your key:
Terminal
printenv OPENAI_API_KEY | codex login --with-api-key
codex login status   # shows which sign-in Codex is using

Run codex login again later to go back to your ChatGPT sign-in once your window resets. One thing that won't help: OpenAI support doesn't reset usage limits.

How to make your Codex usage last longer

These come from OpenAI's own advice on its pricing page:

  • Keep prompts focused and cut context the task doesn't need.
  • Point Codex at the right files rather than the whole repo, and narrow date ranges for anything time-based.
  • Say what you want back: the audience, format and length of the answer.
  • Trim AGENTS.md, and move instructions into nested AGENTS.md files closer to the code they apply to.
  • Turn off MCP servers you aren't using, since each one adds context to every request.
  • Use Standard speed unless you need Fast, given the multipliers above.

For long sessions, /compact summarises the chat so far to free up context, which OpenAI recommends after long runs. If you also use Claude Code, its limits work differently; see our guide to Claude Code usage limits.

Watching Codex usage from the notch

Typing /status works, but only when you remember to. NotchDodo is a Mac app that turns the MacBook notch into a small dashboard, and its AI Usage panel covers Codex CLI alongside Claude Code and Gemini CLI. Here's exactly what it does with Codex, and what it doesn't.

What it shows

  • Every Codex session today, read from the session logs Codex CLI already writes to ~/.codex/sessions on your Mac. Each row shows the project folder, git branch, whether it's Running, Waiting or Done, message count, tokens and time worked.
  • Codex tokens in your totals for today and a seven-day chart.
  • A 5-hour window gauge with tokens used against a budget, burn rate per minute and the time the window ends. The notch flashes when you pass 80% and 100% of that budget, once per window.
  • A live activity in the notch while an agent is running.
NotchDodo AI Usage panel under the MacBook notch, with a current window bar and sessions including orbit-ios running in Codex, tagged GPT, with 88.2k tokens
The AI Usage panel with a Codex session (orbit-ios) next to Claude Code sessions. Demo data.

What it can't show

  • OpenAI's own numbers. The window gauge is NotchDodo's estimate from your local token counts, measured against a budget you set in Settings (or one it picks from your heaviest past window). It isn't the percentage OpenAI shows in /status, and it has no weekly limit. It also pools Claude Code and Codex tokens into one window.
  • Cloud tasks and Codex on the web, since they don't write logs to your Mac.
  • Cost. Codex sessions show $0, because plan usage isn't billed per token.

Separately, NotchDodo keeps your Mac awake while Codex, the Codex app or another agent is working, and can put it to sleep once they finish while the screen is locked. More about keeping your Mac awake for AI agents. For Claude Code there are also notch alerts when it needs your approval.

Which way to check should you use?

/status/usageUsage dashboardNotchDodo
OpenAI's remaining limitsYesNo, token activityYesNo, a local estimate
Weekly limitYes, on plans that have oneWeekly token totalsYesNo
Per-session detailCurrent sessionNoNoEvery local session today
Counts cloud tasksYes, shared allowanceNot statedYes, shared allowanceNo
Visible without askingNoNoNoYes, in the notch
CostFree, built inFree, built inFree$9.99 one-time, with 17 more tools

For the real number, /status and the dashboard are the source of truth, because only OpenAI knows how it weighs each message. If you live in the terminal and want a constant sense of how hard you're pushing, with every session in one place, a glance at the notch saves you asking.

See your Codex sessions in the notch.Sessions, tokens and a 5-hour window gauge for Codex, Claude Code and Gemini CLI, read from local logs. Keeps your Mac awake while agents work. Plus calendar, clipboard, Pomodoro and 15 more tools. One-time purchase, no subscription.Get NotchDodo for $9.99See the AI usage tracker

Sources

Codex, ChatGPT and OpenAI are trademarks of OpenAI. Mac, MacBook and macOS are trademarks of Apple Inc. NotchDodo is an independent app and is not affiliated with OpenAI or Apple.

Frequently asked questions

What is the Codex usage limit on ChatGPT Plus?

Plus has two allowances that run at the same time: a 5-hour window and a weekly window. OpenAI doesn't publish a fixed number. Its pricing page gives estimated ranges of local messages per 5-hour window that depend on the model, for example 15 to 160 for GPT-6.1 Sol and 350 to 3,000 for GPT-6 Luna as of November 2026. Bigger tasks, longer context and Fast mode use it up quicker.

How do I check my Codex usage?

In the Codex CLI, type /status during a session to see your remaining limits. /usage shows your token activity by day, week or in total. For the full picture with reset times, open chatgpt.com/codex/settings/usage in a browser.

When does the Codex 5-hour limit reset?

Five hours after the window started. The window doesn't follow the clock: a new one starts when you send your first Codex or ChatGPT Work message after the previous window has ended. The weekly limit resets on its own schedule, seven days after the weekly period began.

Does ChatGPT Pro have a 5-hour limit in Codex?

Not at the moment. OpenAI says Pro 100, Pro 200 and Pro 500 currently have no five-hour usage limit in Work and Codex, so only the weekly allowance applies. OpenAI has changed this before, so check the help center if it matters to you.

Do Codex cloud tasks and the CLI share the same limit?

Yes. OpenAI says local messages and cloud chats share your plan's usage allowance, and cloud tasks may use more of it than local messages.

What happens when I hit the Codex usage limit?

If you hit it during a turn, Codex can finish that turn, subject to fair use. After that you can wait for the window to reset, use ChatGPT credits, buy an instant reset if your Plus or Pro account offers one, or sign in to Codex with an OpenAI API key and pay standard API rates for extra local chats.

Can OpenAI support reset my Codex limit?

No. OpenAI's help center says support does not reset ChatGPT or Codex usage limits. Your options are waiting, credits, a paid reset where offered, a reset you've earned or been given, or an API key.

Does NotchDodo show my Codex usage?

Yes, from the logs Codex CLI writes on your Mac. NotchDodo reads ~/.codex/sessions and shows each Codex session with its project, branch, status and tokens, adds Codex to your daily and weekly token totals, and counts it towards a 5-hour window gauge with a budget you set. It doesn't show OpenAI's own percentage left or your weekly limit, which only OpenAI knows, and it can't see cloud tasks.