Codex Weekly Limit Reset: Find Your Time or Reset Now
Codex has no fixed reset day. Tibo's 28-day campaign has brought four global resets as of October 20, 2026; Settings → Usage shows whether one reached you.
On this page

There is no universal weekday or hour when every Codex account resets. If Codex says you have reached a weekly limit, open the signed-in account’s Settings → Usage page and read the reset time shown there. Another user’s screenshot, your subscription renewal date, or an announcement about a global reset cannot identify your normal reset time.
Work and Codex share your plan’s usage allowance, including local messages and cloud chats. Plus and Standard Business accounts have a five-hour window, and weekly limits may also apply. Pro plans currently have no five-hour limit, so Pro users run into the weekly limit instead. Included usage is available only while you have allowance left in every window that applies to your plan; eligible accounts may continue with usage credits after reaching those limits. OpenAI’s Work and Codex pricing documentation explains these shared limits and points to the Usage dashboard for current balances and reset times.
Two things changed in October. Tibo, who leads Codex at OpenAI, is running a 28-day campaign that promises one improvement or one full reset each day. As of October 20, 2026, Days 1–15 have brought four global resets and one banked reset. Since about October 15–16, many users have also reported GPT-6.1 Sol using their limits much faster. Those reports cover every reasoning effort, not just Ultra, and OpenAI has not explained them publicly. Both topics have their own sections below.
Check your actual Codex reset time
Use the account and workspace that produced the warning:
- Open Codex on the web or desktop app and go to Settings → Usage.
- Confirm that you are viewing the intended account and workspace.
- Look for every window your plan has, including its remaining allowance and reset time. Plus and Standard Business show a five-hour window and a weekly window. Pro shows only the weekly window, because Pro has no five-hour limit.
- In an active CLI session, run
/statusto check remaining limits. Use the Usage page for reset times and purchase options. - After any reset, refresh Usage and verify each window before starting another large task.
Read the time and timezone when the interface provides them. If Usage shows only a date, it does not establish the exact hour; check again near the displayed reset. A global reset, a full banked reset, or a purchased instant reset can move the weekly date, so an older screenshot or third-party countdown may no longer be accurate.
Do not calculate a weekly message quota by multiplying a published five-hour estimate. Usage varies with the model, task complexity, conversation length, and tools used. Those estimates cannot tell you how many tasks your weekly allowance will cover.
Codex usage meter gone after the app update? Use Settings → Usage
After the late-October updates to the Codex desktop app, the two usage rings in the bottom-left sidebar, just above your profile avatar, are gone. The avatar menu also stopped listing remaining percentages and reset times, and restarting the app doesn't bring either back. GitHub issue openai/codex #57656, opened October 28, 2026, reports the missing rings on Windows after updating to 26.1025.11240. Commenters see the same on macOS with 26.1023.51421, and one Plus user says the rings were there until October 28. GitHub issue openai/codex #56889, opened October 25, covers the avatar menu. Only the display moved. The same five-hour and weekly numbers are still under Settings → Usage, and the #56889 reporter points out that the change affects where usage is shown, not the limits themselves.
Where to read your usage now:
- In the desktop app, open Settings → Usage, as in step 1 above. The countdown there is relative. The #56889 reporter's screen read "5-hour limit: 98% remaining, resets in 4 hours 30 minutes" and "Weekly limit: 84% remaining, resets in 6 days 18 hours". Add the countdown to the current time to get a clock time, so "resets in 4 hours 30 minutes" seen at 9:30 AM means about 2:00 PM.
- In the CLI,
/statusfrom step 4 still applies. None of the update reports mention a change to it. - On an eligible Enterprise or Edu workspace, Settings → Usage & billing in ChatGPT Desktop 26.812.10818 or later shows monthly limits and usage history across Work and Codex, excluding regular Chat usage. OpenAI describes it in Reviewing Work and Codex usage and using Personal Analytics in ChatGPT Desktop.
On October 30, 2026, a test Mac had the desktop app installed at version 26.1023.51421, one of the versions named in #57656. Only the version number was read, so the Usage wording quoted above comes from the #56889 reporter's screen.
As of October 30, 2026, both issues are open and OpenAI hasn't said whether the rings were removed on purpose, while commenters ask for them back or for a setting that keeps them visible.
Five-hour and weekly windows are separate
These windows govern included plan usage. Credits, where supported, can let you continue after that allowance runs out. The five-hour rows apply to Plus and Standard Business. On Pro, the weekly window is the only one that can block you.
| What you see | What it means | What happens next |
|---|---|---|
| Five-hour window exhausted, weekly allowance remains (Plus, Standard Business) | The shorter window has no included usage left | Wait for that window to reset; a weekly-limit banner may not appear |
| Weekly allowance exhausted | No weekly included usage remains | Wait for the timestamp in Usage or review an eligible reset or credit option |
| Both windows exhausted | Both must refresh before included usage can resume | Confirm that any reset you use refreshes both windows |
| Token or context percentage is high | The current session is large | It does not by itself reveal remaining five-hour or weekly allowance |
| An API request is rate-limited | A separately billed API organization, project, or model limit was reached | Diagnose the API error; a Codex subscription reset will not fix it |
For plan-specific checks, the ChatGPT Pro Codex Limit guide explains why Pro has no 5-hour window. The ChatGPT Plus Codex usage limits and credits guide covers the Plus five-hour estimates.
Tibo's 28-day Codex campaign: one improvement or a full reset per day
On October 4, 2026, Tibo (@thsottiaux, "Codex & ChatGPT @OpenAI" on X) announced the 28-day campaign on X: "Over the next 28 days, each day we'll either ship one thing that is a clear improvement and relevant for most codex/work users or ship a full reset." He numbers each post ("Day 1/", "Day 2/", and so on). No end date was posted. Counting 28 days from October 4 puts the end at about November 1, but that is arithmetic, not an announced date.
The campaign exists only in his posts. OpenAI’s help page on how banked Codex resets work was updated on October 20, 2026, and it still lists only the September resets. It also says "Future resets are not guaranteed."
Resets in Days 1–15, by Tibo’s post times (UTC):
| Day | Posted | What Tibo said | Type |
|---|---|---|---|
| Day 3 | October 7 | "Loading a banked reset in everyone's paid accounts" | Banked: you apply it yourself |
| Day 6 | October 10 | "Global reset by EOD"; "All propagated" on October 11 | Global |
| Day 8 | October 13, 01:03 | "Global reset landing by EOD PST time"; "It's done" at 05:06 | Global |
| Day 10 | October 15, 04:55 | "Landing within the next 2 hours"; "Done and dusted" at 06:28 | Global |
| Day 13 | October 17, 16:20 | "Landing sometime today by EOD PST"; Day 13 "Done" post at 21:12 | Global |
The other days shipped improvements. Several of them affect usage. Day 2 made auto-review ("Approve for me") included for ChatGPT sign-in, and the Day 2 roundup says it "does not use usage". Day 7 raised GPT-6.1 Sol’s default context in Codex and Work to 500k, up from 272k, with no long-context fees on subscription usage. Day 11 targeted "Selected model is at capacity" errors, which are not usage limits; the Codex "Selected Model Is at Capacity" guide covers them. Day 12 is discussed in the GPT-6.1 Sol section below.
Three things follow for planning:
- A daily reset is not promised. The promise is "improvement or full reset". Days 14 and 15 (October 19) were an edit-message feature and a livestream, and replies complaining about the missing reset do not change that.
- There is no reset schedule. Global resets have been announced the same day, usually "by EOD PST", and land over the following hours. Reset trackers count Tibo’s posts. They cannot see your account.
- The global resets have no published plan list. Before the campaign, the October 2 reset was for "all paid ChatGPT accounts", and Day 3 said "everyone's paid accounts". Whether Go, Business, Enterprise, or Edu receive every campaign reset is not documented.
Did the global reset reach your account?
A global reset is applied directly to eligible limits and does not show up as a banked reset. Check three things in Settings → Usage:
- The percentages. The windows you had used should be back near full after Tibo’s "done" post.
- The weekly reset time. A global reset restarts the weekly window, so the next weekly reset moves. Logs posted in GitHub issue #54677 in openai/codex show weekly windows re-anchored at about 20:41–20:49 UTC on October 17, which matches Day 13. Those same accounts kept their banked-reset count.
- The banked count. A global reset does not use or add a banked reset. If your banked count dropped, you or an allowed Codex request applied one.
If neither the percentages nor the weekly time changed hours after the "done" post, the reset may have missed your account. That has happened before. On October 3, Tibo posted that some Pro 500 accounts "didn't get the reset as expected" and said he would "make up for it". Business users also reported staying at 0% after a global reset. Tibo’s X replies are where misses have been acknowledged so far. The help page states that Support "does not provide manual or courtesy resets", so screenshots of Usage before and after are your best evidence.
Paying for a reset or saving a banked one during the campaign
Tibo announces a global reset on the same day it lands, so you cannot plan around one. That changes the cost of two common moves:
- Buying an instant reset. If you pay and a global reset lands a few hours later, the purchase bought you only those hours. If the work can wait until the end of the day (PT), check Tibo’s posts first. This is an inference from the timing pattern, not an OpenAI rule.
- Holding a banked reset. A banked reset survives a global reset. That makes it worth keeping for a day when you are blocked and no reset is coming. In the desktop app, the banner for a new grant says it "will expire in 30 days". If the Day 3 reset reached you on October 7, that points to about November 6, but the Expires date in the Usage panel is the one to trust.
What a paid instant weekly reset does
OpenAI now documents an instant paid weekly reset for Work and Codex. It may be offered to eligible ChatGPT Plus and Pro personal accounts on the web or in the desktop app. Availability depends on the account and billing country; the page does not publish one price that applies to everyone.
An eligible account may see the purchase in two places:
- In desktop Settings → Usage after some allowance has been used.
- In an offer shown after the weekly allowance is exhausted. In the desktop app it is titled "You're out of usage" and offers to "Pay {price} to reset your usage limits to 100% immediately" or wait until the reset date. If you also hold a banked reset, the same screen offers "Use available reset" as well.
Successful checkout immediately restores the applicable five-hour and weekly usage windows. Before confirming, understand four consequences:
- The reset applies immediately, even if some included allowance remains.
- It cannot be saved for later or scheduled.
- It pulls the normal weekly allowance forward; it does not create a second weekly allowance on top of the current one.
- The new weekly period begins with the first Work or Codex request after the reset is applied. The next automatic weekly reset is seven days after that request, not necessarily seven days after payment.
For example, suppose checkout succeeds Monday afternoon but you do not send another Work or Codex request until Tuesday morning. Under the documented rule, Tuesday’s first request starts the new weekly period. The next automatic reset is seven days after that request. This example explains the timing rule; your Usage page remains the source for the actual timestamp.

If only the five-hour window is exhausted and the task can wait, check its reset time before paying. OpenAI says weekly reset purchases are generally nonrefundable, subject to the terms and rights that apply to the account and jurisdiction.
The documented paid option is not available to Free, Go, Business, Enterprise, or Edu accounts. Even on Plus or Pro, the absence of a purchase option does not prove that the interface is broken; the offer can vary by account and billing country.
Instant resets, banked resets, and credits are different
The labels can sound similar, but each option changes a different part of the account.
| Option | What it gives you | Does it change the weekly reset? | Can you save it? |
|---|---|---|---|
| Paid instant reset | Immediate restoration of the applicable five-hour and weekly windows | Yes; a new weekly period starts with the first request after application | No |
| Full banked reset | A promotional one-time refresh of eligible five-hour and weekly windows | Yes; the weekly reset date changes | Yes, until use or expiration |
| Usage credits | Pay-as-you-go supported usage after included limits | No; credits do not restart the weekly allowance | They remain a balance under the applicable credit terms |
| Automatic or global reset, such as the campaign resets | A reset OpenAI applies directly | It can refresh the affected window and move the weekly reset time | No stored reset is created |
Use a banked reset only after checking its scope
A banked Codex reset is a promotional benefit stored in an eligible account until it is used or expires. It is not the same as buying an instant reset. Review the offer in Settings → Usage, including its expiration date and the windows it affects, before confirming it.
In the current desktop app, banked resets sit in a Usage limit resets panel under Settings → Usage, with Available and History tabs. The panel reads "Use a reset to restore your 5-hour limit, weekly limit, or both", and each reset shows a Use reset button and an "Expires" date. The panel text does not say whether you can choose one window per reset, and no help page documents that choice. Treat it as a full reset unless the confirmation screen says otherwise.
A full banked reset can refresh both the five-hour and weekly periods and change the weekly reset date. It is consumed only when at least one eligible period is actually refreshed. Eligibility, delivery, expiration, and affected limits can vary by offer, plan, workspace, and region. A past launch promotion is not evidence that another reset will arrive later.
A banked reset is not cash, API credit, a transferable balance, or a permanent increase to the plan. Automatic or global resets are separate events: they can be applied directly without adding anything to the banked-reset balance. Expired resets cannot be restored.
"Allow Codex to use resets": only on request, at 10% or less
The same Usage settings include a switch called Allow Codex to use resets. Its description reads: "Give codex the ability to use a reset when you explicitly request it during a conversation, and your current limit has 10% or less remaining. Resets are never used automatically."
In practice, two conditions must both hold before Codex can spend a banked reset in a chat:
- You ask for it in the conversation, and Codex asks you to confirm each use.
- The five-hour or the weekly window has 10% or less remaining.
If the switch is off and you ask anyway, Codex replies that it "is not allowed to use usage resets" and points you to the setting. If neither window is low enough, no reset is applied, so asking too early costs nothing. Turning the switch on only saves you a trip to the panel mid-task. Leaving it off means every reset is your own click under Usage limit resets.
Credits extend usage but do not restart the clock
Where the account supports them, usage credits let eligible Work or Codex activity continue after included usage is exhausted. They do not reset the weekly allowance or move its reset date. Check the account’s purchase screen for the actual price, supported usage, and terms.
GPT-6.1 Sol eating your 5-hour limit: check plan, effort, and speed
Reports that GPT-6.1 Sol on Ultra "used up my 5 hr limit in 15 minutes" often blur together plan, effort, and speed, and the drain itself is still unexplained. Start with your plan. On Plus and Standard Business, the five-hour window is the one that runs out first. Pro has no five-hour limit, so on Pro the same burn shows up in the weekly meter.
Ultra is a reasoning effort; Ultrafast is a speed mode
In OpenAI’s Codex and Work models documentation, the reasoning effort ladder runs Light, Medium, High, Extra High, then Max and Ultra. The CLI calls Light "Low". "Higher reasoning effort can improve results for complex tasks, but it takes longer and uses more tokens." Ultra "uses subagents to handle separate parts of a complex task in parallel", and the page adds: "Most tasks do not need Max or Ultra."
Speed is a separate setting with published multipliers on included subscription usage:
| Setting | What it changes | Published effect on included usage |
|---|---|---|
| Light to Extra High effort | How much the model reasons per task | No multiplier; higher effort uses more tokens |
| Max effort | More reasoning time on a single task | No multiplier published |
| Ultra effort | Several subagents work on parts of the task in parallel | No multiplier published |
| Fast speed | Faster responses | 2.5x, relative to Standard speed on the same model |
| GPT-6.1 Sol Ultrafast speed | Fastest responses (Pro $500 and eligible Enterprise or Edu only) | 8x, relative to Standard speed |
Many posts say "ultra fast" when they mean Ultra effort, or the other way round. Check both settings before blaming Ultra. If Ultrafast is on, every task draws 8x included usage by design. Ultra’s cost is less predictable. Parallel subagents draw on one shared allowance, so an Ultra run can likely move the meter faster per minute than a single-agent run on the same task. That is an inference from how Ultra works. OpenAI publishes no Ultra multiplier.
The GPT-6.1 Sol vs GPT-6 Astra vs GPT-6 Sol comparison helps if you are deciding which model to run at all.
Reports since October 15–16 are not limited to Ultra
Before mid-October, many Sol users posted the opposite experience. One X user wrote on October 8: "Using Sol 6.1 Ultra the whole day, just 5% of weekly usage." The complaints cluster from about October 15–16:
- An r/codex thread titled "Not sure what they did to GPT 6.1 Sol Usage..." has 110+ comments, including "I had 6.1 sol on ultra use up my 5 hr limit in 15 minutes" and "Sol 6.1 High - 15% used in 10 minutes".
- On X between October 17 and 19, users reported Light burning the five-hour limit faster than Ultra did weeks earlier, Extra High taking 70% of a quota in five hours, and a Pro account draining on High.
- GitHub issue #54677, "Weekly quota jumped 67 points in 38 seconds (Oct 16, 2026; 18:10 UTC)", has 44 comments from Plus, Pro, and Pro 100 accounts, mostly on GPT-6.1 Sol at medium or high effort.
- Issue #54370 (Plus, VS Code, Light) logged 112 tool calls in two turns and 13.9M input tokens, with the five-hour meter moving from 41% to 64% in about 26 minutes.
Not everyone sees it. On October 19, one user reported about 2% used after three hours on Ultra, and another said a Pro 200 weekly limit took over two days to drain on Sol Ultra.
The only explanation on record is a Support reply relayed by one #54677 reporter: "the weekly allowance used to calculate your meter decreased while the amount already consumed initially stayed the same." That account had moved from Pro $200 to $100 on October 6. Others in the thread had no plan change, and no OpenAI staff member has commented in these issues. On October 16, Tibo’s Day 12 post said changes to Codex and Work "increase the effective usage you get", through context reuse across subagents, longer caching, and better routing for cache hits. No OpenAI post connects Day 12 to the drain reports. As of October 20, 2026, the cause is unconfirmed.
One more date affects Pro 200 subscribers. Grandfathered subscribers keep the previous allowance through October 29, 2026. After that, the same work will show as a larger percentage of the weekly limit. That change is expected and is not a bug.
What you can change, and what to record
You control these levers. Each one is cheap to test on a single task:
- Effort. Drop from Ultra or Max to High or Medium for routine work, and try Light for well-scoped edits. Compare the meter after the same kind of task.
- Ultra and subagents. Use Ultra only when the task really splits into parts.
- Speed. Switch Fast or Ultrafast back to Standard unless speed is worth 2.5x or 8x.
- Auto-review. Tibo said on October 6 that auto-review does not use usage. One #55210 commenter still logged 800M tokens on auto-review checks in 12 hours. Turning it off for one task tells you whether it matters on your account.
- Task scope. Long threads, large repositories, and loops with hundreds of tool calls use far more than the prompt suggests. Start a fresh session for a new job. The Codex token usage guide shows how to read
/statusand/usage.
If the meter still jumps on a small task, the change is probably on the server side, and you can’t fix it with settings. Before you contact Support, record:
- Usage percentages and reset times for each window, before and after.
- The time and timezone of the jump.
- Model, effort, speed mode, client (desktop, CLI, IDE, web), and version.
- Whether auto-review or subagents ran, plus tool-call and token counts if
/statusshows them. - Any credits charged after the limit hit zero.
That last item matters. In issue #54767, closed as a duplicate of #54677, a Pro user went from 48% to 0% in nine minutes and was then charged 295.8 credits. A banked reset applied afterward did not stop the drain. If your account can spend credits after the limit, a fast drain carries on into paid usage. Watch the credit balance while you test. A banked reset spent during an unexplained drain may disappear just as fast.
Choose the least disruptive way to resume work
| Your situation | Best next check |
|---|---|
| The task can wait | Note the blocking window’s reset time in Usage and resume afterward |
| A five-hour window is the only blocker | Wait for that window unless an immediate reset is worth its account-specific price |
| Tibo has announced a global reset for today | Wait for his "done" post and recheck Usage before paying or using a banked reset |
| An eligible paid instant reset is offered | Review the immediate application, new weekly-cycle timing, and checkout terms before buying |
| A banked reset is available | Check its expiration and affected windows, then use it only when the refresh is valuable |
| Usage drains far faster than last week on GPT-6.1 Sol | Lower effort, turn off Ultrafast or Fast, test one small task, and record the meter before spending a reset |
| Credits are available | Confirm the supported activity and price; remember that the weekly clock does not restart |
| A local task supports API-key sign-in | Check separate API charges, limits, and supported features before switching |

When usage remains, you can often make the allowance last longer by narrowing the task, starting a fresh session when the old conversation is no longer useful, or choosing a lighter model or a lower effort for a simple job. These choices reduce future consumption; they do not restore an exhausted allowance.
API-key usage is a separate billing route
Local Codex supports API-key sign-in, with separate OpenAI Platform billing and rate limits. It does not use or replenish your subscription allowance, banked resets, or Work/Codex credits. API rate limits can still stop a request even when the API account has funds.
Codex cloud requires ChatGPT sign-in, so an API key cannot replace a subscription for every task. Check the API key versus subscription guide for supported features and billing differences before switching.
If an API request fails, check its error message rather than buying a Codex subscription reset. The API rate-limit troubleshooting guide explains when to retry, reduce request volume, or check billing.
If a reset was applied but Codex still looks blocked
First, refresh or reopen Usage and verify the account and workspace. Then compare the five-hour and weekly windows individually. A reset of one window may leave the other exhausted, and an old page can continue displaying stale data.
For a purchased instant reset, confirm that checkout actually succeeded. For a banked reset, confirm that the offer covered the window you expected and that at least one eligible period was refreshed. For a global reset, check whether the weekly reset time moved. If the percentages recovered but the meter fell again within minutes, the problem is the drain described in the GPT-6.1 Sol section, not the reset. After a reset, rely on the newly displayed times rather than calculating them from the previous schedule.
If the discrepancy persists, contact OpenAI Support with the account and workspace, the type of reset, the purchase or application time and timezone, the client used, and screenshots of Usage before and after. Do not post receipts, full account identifiers, or API keys in a public forum.
Frequently asked questions
Did Codex reset today?
Check whether the remaining weekly allowance and timestamp changed in Usage. During Tibo’s 28-day campaign, global resets are announced on his X account (@thsottiaux) on the same day, and as of October 20, 2026, the latest one landed on October 17. A news post, tracker, community screenshot, or automatic reset affecting other accounts is not proof that your account reset. Also check the five-hour window, because it can remain the active constraint.
Does Codex reset every day now?
No. The campaign promises one improvement or one full reset per day, not a reset every day. Days 1–15 included four global resets (Days 6, 8, 10, and 13) and one banked reset (Day 3). The rest were product improvements.
When is the next Codex reset?
Your next normal weekly reset is the time shown in Settings → Usage. That time moves after any global, banked, or purchased reset. No schedule exists for campaign resets. Tibo has posted each one on the day it landed.
Does ChatGPT Pro have a 5-hour limit in Codex?
No. OpenAI’s pricing documentation says Pro plans currently have no five-hour limit. Pro users are limited by the weekly window, which is why heavy GPT-6.1 Sol use on Pro shows up as a weekly-meter drop.
Why do I not see the paid reset after hitting the five-hour limit?
Exhausting only the five-hour window does not trigger the weekly-limit offer. An eligible desktop account may still show an option in Settings → Usage after some allowance has been used, but availability varies. If no option appears, wait for the displayed window or use another option that the account actually provides.
Sources13
External pages this guide links to, in the order they appear. Last updated Oct 30, 2026.
Sources13
External pages this guide links to, in the order they appear. Last updated Oct 30, 2026.
- 1.Work and Codex pricing documentationlearn.chatgpt.com/docs/pricing
- 2.Usage dashboardchatgpt.com/codex/settings/usage
- 3.GitHub issue openai/codex #57656github.com/openai/codex/issues/57656
- 4.GitHub issue openai/codex #56889github.com/openai/codex/issues/56889
- 5.Reviewing Work and Codex usage and using Personal Analytics in ChatGPT Desktophelp.openai.com/en/articles/20001478
- 6.@thsottiauxx.com/thsottiaux
- 7.announced the 28-day campaign on Xx.com/thsottiaux/status/2106845241357824205
- 8.how banked Codex resets workhelp.openai.com/en/articles/20001498-how-banked-codex-resets-work
- 9.Day 13 "Done" postx.com/thsottiaux/status/2111566005684289735
- 10.GitHub issue #54677 in openai/codexgithub.com/openai/codex/issues/54677
- 11.instant paid weekly reset for Work and Codexhelp.openai.com/en/articles/20001507-paid-weekly-work-and-codex-rate-limit-resets
- 12.Codex and Work models documentationlearn.chatgpt.com/docs/models
- 13.Day 12 postx.com/thsottiaux/status/2111244596131111253





