AI News

Reset monitor

Follow Tibo and Andrew at OpenAI for Codex usage resets and reset credits, timing, eligibility and original announcements.

All times in Beijing · UTC+8

Last reset credits: 2026-11-13

No announced reset is waiting to take effect

Estimated 11/13 08:30–11/13 13:30 UTC+8

We do not predict unannounced resets. New official announcements will appear here with their source. Check your personal quota in Codex.

Tibo@thsottiauxUpdate

We shipped some good updates to dots today and the banked reset has been activated and should land in everyones accounts sometime soon!

Quoting @ChatGPT

Your dot now has… ⚡️ Faster replies 💬 Less jargon 🫡 Better follow-through And, they can now follow your custom instructions. Tell your dot in the thread things like how to behave or which actions need your go-ahead. “always talk in lowercase.” “Show me a draft before sending any emails.” You can also set custom instructions and rules in Customize > Behavior on mobile, or through your dot’s menu on web and desktop.

Usage resets · 90 days
21
Reset credits · 90 days
11
Median reset interval
2.1 days
Last usage reset
2026-10-28

Reset calendar

Choose any date to see records and source posts.

Browse 61 recorded dates
Recent source posts132 public records
Tibo@thsottiaux

This celebration is moved to tomorrow as the button was already pressed today.

Quoting @thsottiaux

Looking at the dashboard we might hit a new milestone to celebrate tomorrow. Hold on to your Codex

Tibo@thsottiaux

@ChrisGPT Tell them Chris. Tell them! You're vindicated

Reply to @ChrisGPT

@thsottiaux “Depending on how you use Codex, you should see your usage go between 10% and 50% further than before.” And they all thought I was crazy tibo!

Reply to @thsottiaux

We are reseting usage for all paid users of Codex and ChatGPT Work. Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes. Depending on how you use Codex, you should see your usage go between 10% and 50% further than before. We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed: - Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed. - Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed. - Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed. - Automations. Some custom schedules could run more frequently than configured. Fixed. - Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed. - Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed. - Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this. - MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed. We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess. Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!

Tibo@thsottiauxAnnouncement

Landing 2:30pm PST

Reply to @thsottiaux

We are reseting usage for all paid users of Codex and ChatGPT Work. Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes. Depending on how you use Codex, you should see your usage go between 10% and 50% further than before. We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed: - Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed. - Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed. - Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed. - Automations. Some custom schedules could run more frequently than configured. Fixed. - Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed. - Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed. - Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this. - MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed. We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess. Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!

Tibo@thsottiauxAnnouncement

We are reseting usage for all paid users of Codex and ChatGPT Work. Please continue reading for an update on Codex usage limits. The team has been working around the clock, going through thousands of reports and shipping fixes. Depending on how you use Codex, you should see your usage go between 10% and 50% further than before. We really went with a fine comb, with many uncovered small things being longstanding and here is what we found and fixed: - Compaction. We were keeping old images during compaction, sometimes making the context large enough to trigger compaction again. After the fix, usage dropped around 10% for users making heavy use of images. Fixed. - Memory. Background memory workers could inherit Stop hooks and keep running when the hook wouldn’t let them finish. This affected fewer than 1% of users, with the long tail being pretty bad and we saw one example thread check whether it could stop 15,000 times. Fixed. - Goals. In some cases, a set /goal could finish and then keep going past the intended stop condition, or the model would keep retrying broken tools without stopping. We saw examples consume anywhere from 15% to 70% of a weekly allowance. Fixed. - Automations. Some custom schedules could run more frequently than configured. Fixed. - Subagents. Smaller models (e.g. Luna) sometimes picked more capable helpers without being explicitly asked. The same was true where the orchestrating model not running in /fast mode could request sub-agents to run /fast. Fixed. - Computer History. The older implementation could lead to repeatedly summarizing overlapping activity. For some cases we saw it consume up to one fifth of the weekly usage per week. Fixed. - Rolling task summaries. Ordinary turns were triggering extra background requests. These added about 1% to token usage. Small each time, but it adds up. We have disabled this. - MCP. Some tool results could be encoded twice. We also found tool instructions getting cut off and fetched again. Fixed. We’ve also made architectural changes to prevent these from regressing and our teams will get paged if it happens regardless. We are also working on showing you directly in the app where your usage goes so you don’t have to guess. Goes without saying that we’re resetting usage limits and I hope you enjoy a very nice Saturday!

Tibo@thsottiaux

Codex team might have actually fixed the "model at capacity" errors that have been pestering you. https://t.co/EgS0HkOATY

Tibo@thsottiauxUpdate

We shipped some good updates to dots today and the banked reset has been activated and should land in everyones accounts sometime soon!

Quoting @ChatGPT

Your dot now has… ⚡️ Faster replies 💬 Less jargon 🫡 Better follow-through And, they can now follow your custom instructions. Tell your dot in the thread things like how to behave or which actions need your go-ahead. “always talk in lowercase.” “Show me a draft before sending any emails.” You can also set custom instructions and rules in Customize > Behavior on mobile, or through your dot’s menu on web and desktop.

Tibo@thsottiauxCredit announcement

Thursday is feeling codexy to me. Perhaps also a good time for a banked reset.

Reply to @thsottiaux

It’s been a while without resets. Maybe I should come back out of the basement

Tibo@thsottiaux

@Tech_girl We doubled the usage on Pro plans and Business 100

Reply to @Tech_girl

Has anyone else noticed that ever since Tibo stopped giving out resets, Codex usage limits seem to last longer? Or is it just me?

Tibo@thsottiauxCredit announcement

Day 28/ Banked 2/2

Tibo@thsottiauxCredit announcement

Banked 1/2

Tibo@thsottiauxCredit announcement

Day 26/ You can now easily switch between multiple accounts on mobile, and coming soon to desktop too. Next two days will be resets… banked… do with this what you may 👀. https://t.co/iQxsqbuk0f

Tibo@thsottiaux

@claudeai Better announce 28 days of reset

Reply to @claudeai

We’re renaming our Max plans: Max 5x → Max Max 20x → Ultra Max is still $100/month, and Ultra is still $200. If you’re a subscriber, there’s nothing you need to do. We’re also removing the 5-hour limit for verified Ultra accounts, starting today with most existing subscribers. Newer accounts keep a temporary limit until they’re verified, which helps us prevent fraud and abuse. You'll get an email when it's removed. Weekly limits remain unchanged. View our plans here: https://t.co/niRpyGF5Me

How is the timing estimated?Sources and rules

Explicit times, relative hours and deadlines are interpreted in America/Los_Angeles and converted to Beijing time, with a small allowance for rollout delay.

Date-only Codex announcements use the usual Pacific evening window. This remains an estimate.

After an estimated window ends, records await confirmation for six hours, then show likely completion. An estimate never becomes an officially confirmed fact.

Reset credits and direct usage resets are separate: receiving a credit does not automatically restore usage.

The configured scan interval is ten minutes. Source announcements, not this page, determine eligibility; personal usage is only available in the product.

Records begin 2026-04-01
Needs attention · Last checked 11/16 22:55AI News · Not affiliated with OpenAI
Last attempted read
11/16 22:55
Last posts collected
11/16 14:14
Last complete check
11/16 22:55