DEV Community: Codex Reset

How Codex usage limits work: two windows, three kinds of reset

Codex Reset — Thu, 05 Nov 2026 02:00:07 +0000

Disclosure: we build Codex Reset. This post explains how Codex limits and resets work, using OpenAI's own pricing page and Help Center as the source, and points to the pages on our site that track them.

Most of the confusion around Codex limits comes from one word doing too many jobs. "Reset" can mean your 5-hour window rolling over, your weekly window rolling over, a reset OpenAI applies to many accounts at once, a reset saved in your account, or one you buy. They behave differently, and some of them move your next reset date.

The last post covered where to get reset alerts. This one is the background: what the windows are, what OpenAI does and doesn't publish about them, and what each kind of reset actually changes. Everything below comes from OpenAI's pages as of November 5, 2026. OpenAI updates them often, so treat the links as the authority and our summary as a map.

Two windows, one pool

On most paid plans Codex runs two limits at once: a 5-hour window and a weekly window. The same usage counts against both, but the two periods can end at different times. OpenAI's own example: your weekly period could end at noon while your current 5-hour period runs until 3 p.m.

That's why clearing one doesn't fix the other. If your weekly window is exhausted, a fresh 5-hour window won't unblock you. You need the weekly rollover, a reset, or credits.

The pool is also bigger than Codex. Where your plan has them, Codex, ChatGPT Work, ChatGPT for Excel and Workspace Agents share one allowance and credit pool, so a long ChatGPT Work session spends the budget your coding session needs. Local messages from the CLI, IDE extension or desktop app share it with cloud chats, and cloud tasks may use more of it than local messages.

Plans differ in which windows they have:

Plus and Business Standard: a 5-hour allowance and a weekly allowance.
Pro (100, 200 and 500): the pricing page says "Pro plans currently have no five-hour limit", so Pro runs on the weekly allowance.
Go: a monthly allowance.
Enterprise and Edu with flexible pricing: no fixed rate limits; usage scales with credits.

What the 5-hour numbers mean

The pricing page lists local messages per five-hour period for Plus and Standard Business. The ranges are wide: GPT-6.1 Sol 15–160, GPT-6.1 Terra 35–285, GPT-6 Astra 5–45, GPT-6 Luna 350–3,000.

OpenAI's caveat is the important part: "These estimates are not fixed message limits." What a message costs depends on the model, where the task runs, how complex it is, the context, reasoning, speed and tools. A long-running agent task can use far more than a short request. Read the ranges as a sense of scale, not as a counter.

The weekly window has no published size

For the weekly window OpenAI publishes no number for any plan. The pricing page says only "Weekly limits may also apply." Anyone quoting an exact weekly cap is estimating.

People do try to measure it. Our /codex-usage page collects those measurements, converts one full week into API dollars per plan and cites every figure. OpenAI warns against that kind of conversion: "API token prices are separate from subscription usage; don't use them to estimate included tasks." So we show the table as a rough scale, with each row's source next to it.

"Codex limits by plan, with sources" on codex-reset.com/codex-usage (screenshot, November 5, 2026). The dollar figures are third-party measurements, not OpenAI numbers.

Where to check your own numbers

Your own balance is the only number that counts. OpenAI points to these places:

In an active Codex CLI session, run /status.
On the web, ChatGPT Settings → Usage (chatgpt.com/settings/usage).
In the desktop app, Settings → Usage & billing.

When you hit a limit, the notice shows the options your account has: add credits, use an available reset, upgrade, or wait until the displayed reset time.

Three kinds of reset

OpenAI's article How resets work in Codex separates three one-time resets, all distinct from the regular scheduled refresh:

Banked reset. Free, one-time, saved to your account for later. Receiving one does not refresh your usage. You choose when to use it, before it expires.
Automatic reset, "sometimes called a global reset". Applied directly to the accounts and limits an offer selects. You don't redeem it and it isn't saved. In OpenAI's words: "'Global' does not mean every account or every usage limit."
Purchased reset. Bought for immediate use and offered to selected Plus and Pro personal accounts.

None of them permanently raises your limits. Free banked and automatic resets have, as OpenAI puts it, "no guaranteed availability or schedule". That uncertainty is what our site tracks: it reads the public announcements, shows a forecast, and confirms when a reset has actually reached the accounts we monitor.

Grant, redemption and automatic reset compared on codex-reset.com/banked-reset (screenshot, November 5, 2026).

Using a banked reset

You can redeem a banked reset in the desktop app (Settings → Usage & billing), on the web (Usage settings), or in Codex CLI by entering /usage and choosing Redeem reset. The mobile app doesn't offer it, and older CLI versions may not show the option.

A few rules catch people out:

From Usage settings, at least one covered allowance must have less than 80% remaining. Otherwise you see "Your usage does not need a reset right now" and the reset stays in your account.
A full banked reset brings each covered allowance that is below 100% back to 100%. An allowance already at 100% isn't restarted. On Plus that covers the 5-hour and weekly allowances; on Pro, the weekly allowance.
It only counts as used if it restores at least one allowance.
Separate allowances such as image generation, file upload and regular Chat Voice stay as they were.
A desktop option, "Allow your assistant to use resets", lets Codex redeem one itself once your main 5-hour or weekly allowance is at 10% or less.

Use it before the expiry shown in your account or offer. Our banked reset page has an expiry tracker and a checklist for when a reset looks missing.

Why your weekly date moved

This is the most common surprise. Banked, global and paid resets can all change your next refresh time, and "the new schedule replaces the old one." OpenAI's example: a weekly period that was due to end on Friday restarts on Tuesday, so it now refreshes the following Tuesday, and the Friday refresh no longer applies.

So OpenAI's advice is to read the next refresh time in Usage instead of working it out from when you redeemed, bought, or saw an announcement. Before a new period starts, the displayed time can itself be an estimate.

Two related points from the same article:

A global reset after a banked one brings the allowance back to 100%, not 200%. The banked reset you used isn't returned, and any unused ones keep their original expiry.
The desktop History view shows banked-reset activity for the past 30 days. Paid and global resets don't appear there, so a missing entry doesn't mean you missed a global reset.

Paid resets

Eligible Plus and Pro personal accounts can buy an instant reset from desktop Usage settings, or from an offer that appears after reaching the weekly limit. It isn't available on Free, Go, Business, Enterprise or Edu, and availability varies by account even on the same plan.

A purchase restores both 5-hour and weekly usage at once. It pulls your normal weekly allowance forward rather than adding usage, can't be saved for later, and is generally not refunded. Your new weekly period starts with your first Work or Codex request after the reset, and the next automatic weekly reset is seven days after that request. It applies even if you still have usage left, and it changes your weekly reset schedule.

Where Codex Reset fits

Our site never reads your OpenAI account. The /codex-usage tracker lets you paste /status or type your weekly percentage and reset time, and keeps that in your browser. Its main job is the part OpenAI doesn't schedule: watching for automatic and banked resets and confirming when one has reached the Pro and Plus accounts we monitor. The alert channels are covered in the previous post.

What it can't do: it can't see your personal limits, it doesn't cover Team or Business workspaces, and it can't tell you whether a given offer included your account. For that, your own Usage page is the authority.

Quick answers

My weekly allowance is empty. Does a fresh 5-hour window help? No.
How big is the weekly limit? OpenAI doesn't publish it.
Does receiving a banked reset refresh my usage? No. Only redeeming it does.
Why did my weekly reset date change? A reset restarted the period. Check Usage for the new time.
Does a global reset reach everyone? Not necessarily. OpenAI says "global" doesn't mean every account.

Codex Reset is an independent community tracker and is not affiliated with OpenAI. "Codex" is a trademark of OpenAI.

Get Codex reset alerts wherever you already are

Codex Reset — Wed, 04 Nov 2026 23:58:50 +0000

Disclosure: we build Codex Reset. This is a guide to its alert channels from the people who run it, including what they can't do.

If you use Codex heavily, you have probably watched your weekly limit drop to a few percent halfway through a task. OpenAI hands out global resets from time to time, and almost all of them are announced on X by Thibault Sottiaux (@thsottiaux, usually called Tibo), who leads Codex. So the default move is to keep refreshing his profile.

Codex Reset reads those public posts for you, checks Codex Pro and Plus accounts that we own to see when a refill has actually landed, and sends the result to the channel you pick. It never touches your OpenAI account, and you don't need an account with us. Earlier posts covered how we read Tibo's posts and how our own accounts confirm that a reset has landed.

This one is practical: where you can get the alerts, how quickly each channel tends to arrive, and the small catches.

What counts as an alert

Before picking a channel, it helps to know what will reach you. The alerts menu on the site sums it up in one line: "⚠️ strong Tibo signal · ✅ verified reset · 🎟️ banked reset — resets only, nothing else."

The alerts menu on codex-reset.com, open over the homepage (screenshot, November 4, 2026).

In practice that means a handful of message types:

⚠️ Watch: Tibo has made a clear promise. It comes with a probability: 93% when his words give a time window, 83% when they don't.
⌛️: Tibo says the reset is done, and our accounts haven't confirmed it yet.
✅: the refill reached the Pro and Plus accounts we monitor. There is one exception, covered under limits below, and the message says when it applies.
🔬: our accounts measured a reset that nobody announced.
🎟️: a banked reset update.

A real ✅ from the public Telegram channel is headed "✅ Codex reset confirmed" and reads "Our checks show that Codex usage limits reset around 06:35 UTC on Oct 28." Times are given in UTC.

Tibo's hints and teases (👀) are not alerts. They show on the site, and our X account posts them, but Telegram, Discord, email and push stay quiet. If you only want to hear about resets, any of the main channels will do that.

t.me/codexresetalerts is the alerts channel. Open the link and join. It's a broadcast channel, so you only receive messages.

Telegram is one of the instant channels. It carries regular resets, strong Watches and qualifying banked updates. One detail makes it calmer than it sounds: when Tibo replies to his own post with a landing time, we edit the existing ⚠️ message with the new deadline instead of sending another one. You don't get pinged twice for the same reset.

Pick Telegram if it's already open on your phone or desktop all day.

Discord

The Discord invite takes you to the Codex Reset server and drops you in #alerts. That channel carries the same alerts as Telegram, and the same in-place edit applies when a landing time arrives.

Discord fits if your team or coding community already lives there. Discord lets you turn on notifications for #alerts and mute the rest of the server, which keeps it to resets only.

Email

Email starts at notify.codex-reset.com. Enter your address and we send a confirmation link. Opening the link doesn't subscribe you on its own. You have to press the confirm button on the page it opens.

The email subscription page at notify.codex-reset.com (screenshot, November 4, 2026).

The confirmation comes from alerts@notify.codex-reset.com. The sending domain is new, so check Spam if it doesn't show up. If it's there, marking it "not spam" helps later alerts reach your inbox.

After that you get one email for each confirmed reset, high-confidence forecast or qualifying banked-reset update. Two caveats are worth knowing:

Email is the slowest lane. Messages go out in batches, and inbox providers add their own delay. An email can arrive minutes after the same alert is on Telegram, Discord or push.
Delivery is at-most-once. In a rare, ambiguous failure at the email provider, you might miss one message. The system won't send a duplicate to make up for it.

The emails are transactional only: no sponsored content, affiliate placements, personalization or tracking. Each one has an unsubscribe link, and mail apps that support one-click unsubscribe will show that button too.

Email suits you if you'd rather not install anything, or you like a record you can search later. Skip it if a few minutes matter to you.

X

@codex_reset posts each alert (⚠️ ⌛️ ✅ 🎟️). It's also the one channel that posts Tibo's teases (👀), so it's a little busier than the others. The account checks the site's public data once a minute, so expect a short lag behind the instant channels.

Following the account is not enough to get notified. Turn on notifications for it in X, or the posts just wait in your timeline.

Pick X if you're on it anyway, or if you want the teases as well as the alerts.

Browser push

On codex-reset.com, open the alerts menu and turn on browser notifications. You don't need an account.

Push wakes your browser for the latest regular reset, strong Watch or banked update. If several things happen in a row, you may only see the latest state rather than every step. Old alerts never replay.

On iPhone, push only works after you add the site to your Home Screen and open it from there.

Push fits if you sit at the same computer all day and don't want another app.

Quieter options

The Atom feed. codex-reset.com/feed.xml lists Tibo's reset announcements. Each entry quotes his post and links to it on X. It's meant for feed readers and scripts. It records what he announced, not what our accounts measured, so for ✅ and 🔬 use one of the channels above.

The Tibo streams. If you want to read Tibo's posts yourself without opening X, Codex Reset · Tibo Radar on Telegram and #tibo on our Discord pass them along with little noise. They're separate from #alerts and don't mirror it. Think of them as context, not alerts.

Chinese readers can join our QQ group from the Chinese version of the site. It isn't an automatic alert channel, so pair it with one of the channels above.

Build your own alert

If none of these fit, the developer page documents a public JSON API and a read-only MCP server. In the page's words: "No key, no sign-up, no rate plan — the one condition is credit." If you show the data to other people, name the source and link it on the same surface ("Data: codex-reset.com"). A private script or a cron job that pings your own phone only needs a User-Agent that names your project.

The page's own example reads the current forecast:

curl -sS https://codex-reset.com/api/forecast \
  -A 'myproject/1.0 (+https://myproject.example)' \
  | jq '{p24: .probabilities.rounded_24h, p48: .probabilities.rounded_48h, last: .last_reset_at}'

If you'd rather ask your coding agent, add the MCP server. In Claude Code:

claude mcp add --transport http codex-reset https://codex-reset.com/mcp

Codex CLI and the IDE extension read ~/.codex/config.toml:

[mcp_servers.codex-reset]
url = "https://codex-reset.com/mcp"

Then ask "did Codex reset today?" between tasks. We walked through the terminal side in more detail in an earlier DEV post. The full reset history is also published as an open dataset under CC BY 4.0 on Hugging Face and Kaggle.

Which one to pick

You want to know within minutes and Telegram is always open: Telegram.
Your team is on Discord: Discord #alerts.
You're at one desk all day and don't want to install anything: browser push.
You want a searchable record and minutes don't matter: email.
You're on X a lot, or you want the teases too: @codex_reset.
You want it inside your own tooling: the API or MCP server.

One channel is enough. The main channels carry the same alerts, so subscribing to three just means hearing about the same reset three times.

What the alerts can't tell you

A few limits apply to every channel.

We monitor Pro and Plus. Our accounts are ChatGPT Pro and Plus. We don't cover Team or Business workspaces yet, so a ✅ tells you nothing about them.

A ✅ can rest on Tibo's word. If our monitors can't take a reading, a ✅ based on Tibo's confirmation says so in the message: "Our monitor hasn't measured it yet."

A Watch is a probability. 93% is likely, not certain. It's there to help you decide whether to wait or wrap up.

Some lanes trade detail for reliability. Email can very rarely miss a message, and push may show only the latest state. If you need every step, Telegram or Discord is the better fit.

Pick the channel you already check, and get back to work.

Codex Reset is an independent community tracker and is not affiliated with OpenAI. "Codex" is a trademark of OpenAI.

Is a Codex usage-limit reset coming? Check from your terminal with a free API (or MCP)

Codex Reset — Thu, 24 Sep 2026 02:24:07 +0000

If you use OpenAI Codex a lot, you've probably hit the weekly limit and asked the same question everyone asks: is a reset coming, or should I just wait it out?

There are two different kinds of "reset", and people mix them up:

Your own windows. Codex meters usage per account, in a rolling window that starts from your first request. /status inside Codex shows when yours rolls over. Nobody else can predict it for you.
Global early resets. Every so often OpenAI resets everyone's limits early: after an incident, a bug that drained usage, or just a milestone. These are announced informally on X, with no schedule and no status page.

This post is about the second kind. codex-reset.com tracks those announcements, keeps a dated record with source links, and publishes a probability that another one lands in the next 24 or 48 hours. All of it is available as free JSON with no API key, and as an MCP server you can plug into Codex itself. Below is how to use both from a terminal.

Disclosure: this account belongs to the project. Everything below is free to use; the only condition is a visible credit if you show the data to other people.

1. "Is a reset likely soon?"

curl -sS https://codex-reset.com/api/forecast \
  -A 'my-script/1.0 (+https://example.com)' \
  | jq '{p24: .probabilities.rounded_24h, p48: .probabilities.rounded_48h, confidence, last: .last_reset_at}'

{
  "p24": 20,
  "p48": 35,
  "confidence": "low",
  "last": "2026-09-12T08:09:17.000Z"
}

That's a percentage chance of a global reset within 24h and 48h, how confident the model is, and when the last confirmed reset happened. It's a forecast, not a promise: treat 20% as "probably not today".

The -A header matters. Server-side readers are asked to send a User-Agent that names the project, so the site can tell real integrations from anonymous scrapers.

2. "When was the last reset, and where was it announced?"

Every entry in the record links to the original post:

curl -sS https://codex-reset.com/api/timeline \
  -A 'my-script/1.0 (+https://example.com)' \
  | jq -r '[.events[] | select(.group == "reset" and .announcement_state == "announced")]
           | sort_by(.announced_at) | reverse | .[0:3][]
           | "\(.announced_at)  \(.url)"'

2026-09-12T08:09:17.000Z  https://x.com/thsottiaux/status/2098685367058612394
2026-09-08T01:34:00.000Z  https://x.com/thsottiaux/status/2097043464538264003
2026-08-31T02:34:27.000Z  https://x.com/thsottiaux/status/2094252447271366730

The announcement_state == "announced" filter matters. A post that only promises a reset shows up in the record too, but a reset only counts once it's actually announced. That's the same rule the site's ✅ alerts use.

3. "Is Codex down, or did I hit my limit?"

When Codex starts failing, check whether it's an outage before you blame your quota:

curl -sS https://codex-reset.com/api/status-history \
  -A 'my-script/1.0 (+https://example.com)' \
  | jq -r '.current.surfaces[] | "\(.label): \(.status)"'

Codex Web: operational
Codex API: operational
Codex CLI: operational
VS Code extension: operational
Codex in ChatGPT Desktop: operational

4. Ask Codex directly (MCP)

The same data is exposed as a read-only MCP server over Streamable HTTP. There's nothing to install, no key, and no account. Add it to ~/.codex/config.toml:

[mcp_servers.codex-reset]
url = "https://codex-reset.com/mcp"

Or in Claude Code:

claude mcp add --transport http codex-reset https://codex-reset.com/mcp

Then just ask, in the agent:

"Is Codex likely to reset its usage limits in the next 24 hours?"
"When was the last verified Codex reset, and where was it announced?"
"Is Codex down, or did I just hit my usage limit?"

There are three tools, get_reset_forecast, get_reset_timeline and get_codex_status, all read-only. Config for Cursor, VS Code and others is in the codex-reset-mcp repo. The repo also installs as a Codex plugin.

5. A tiny "tell me when it resets" script

The record only changes when a reset is announced, so a watcher just compares last_reset_at:

#!/usr/bin/env bash
# Poll politely: the data refreshes about once a minute; every 5 minutes is plenty.
UA='reset-watch/1.0 (+https://example.com)'
last=""
while true; do
  now=$(curl -sS -A "$UA" https://codex-reset.com/api/forecast | jq -r '.last_reset_at')
  if [ -n "$last" ] && [ "$now" != "$last" ]; then
    osascript -e 'display notification "Codex limits were reset" with title "Codex"' 2>/dev/null \
      || notify-send "Codex limits were reset" 2>/dev/null \
      || echo "Codex limits were reset at $now"
  fi
  last=$now
  sleep 300
done

If you'd rather not run anything, the site also pushes the same event to Telegram, Discord and browser notifications.

Using the data in your own tool

The API is free and keyless, with CORS open. The terms fit in one line: if you show the data to people, credit it where it appears (Data: codex-reset.com, linked), and send an identifying User-Agent from servers. Field reference and polling guidance: codex-reset.com/developers.

Several open-source menu-bar apps and bots already read it this way. If you build something on it, I'd like to hear about it in the comments.