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 posts136 public records
Tibo@thsottiaux

(1) is not correct, it is not due to 2X charging after 272k context, we don't charge for longer context on the subscription for GPT 5.6 Sol as we control all the settings. It is due to something else, which I will attempt to explain below. The overall trajectory length, which is the total some of all context windows across compactions, changes little based on the reasoning effort. Similarly the quality of the overall output is similar across context lengths above 272k. The benefits of higher context lengths are mostly overall speed (as you don't wait for compaction), ability to deal with humongously large input and potentially cost if the system is well tuned and you hit your cache perfectly. The actual reason is the what you can see depicted in the chart below, which is the difference in the orange line and the blue line. It is caused by overall cost of cache reads going up with the size of the context being shuffled back and forth between toolcalls. The sweet spot in terms of cost is therefore not necessarily to use the maximum possible context length. What we're working on is tuning the system differently so that we can go back higher without it resulting in higher usage being charged. Hope this clarifies a bit.

Reply to @theo

There's a few issues with Codex that stacked really badly, causing people's usage to get nuked. Crazy how well they all lined up to be as rough as possible Issue 1 (shown here): gpt-5.6 costs 2x more after 272k tokens. Codex upped their limit to 372k tokens, meaning long threads were billed 2x higher Issue 2: "Ultra" subagents were also spawned with Ultra, causing insane nested subagent usage that burned a TON of tokens. Apparently intended, but (hopefully) being toned down in system prompt Issue 3: Sol and Terra use the "v2" subagent layer in Codex that is still early/unfinished/disabled by default. v1 spawned subagents with a fresh history, v2 copies the entire long context. When combined, you end up with: 1. A ton of reasoning tokens filling context windows, triggering 2x billing 2. Subagents spawning with that filled context window, instantly billed at 2x 3. Ultra spawning too many of these high reasoning full-window subagents If you had fast mode on when this happened, you got hit with an ADDITIONAL 2.5x No wonder we were burning so hard...

Quoting @thsottiaux

Updates for Codex and ChatGPT Work users. No nerfing, only good stuff! - We have landed inference optimizations and are passing down savings to all the subscriptions for GPT-5.6 Sol. That should result in around 10% more usage on its own. - We noticed that by changing the context size limit in the product to 372k for GPT-5.6 Sol, up from 272k for GPT-5.5, it resulted in more usage being charged than intended. We have reverted to 272k and will work to roll back out to 372k in the days to come. You should notice that usage drains significantly less after this change. - To understand where the extra usage was coming from, we ran some experiments where reasoning efforts were changed (referred to as juice values under the hood) and have reverted this. - There is slightly more usage of multi-agent than intended in high and xhigh reasoning effort, we are fixing this going forward. Also fixing a small other thing we noticed with auto-review where we can be more efficient. And we continue to have the 5h limit temporarily not apply. Enjoy the rest of the weekend!

Tibo@thsottiaux

@iruletheworldmo @AniBaddepudi Always the small propagation delay. Check now?

Reply to @iruletheworldmo

@thsottiaux @AniBaddepudi https://t.co/6YWGjMO9ZS

Reply to @thsottiaux

Updates for Codex and ChatGPT Work users. No nerfing, only good stuff! - We have landed inference optimizations and are passing down savings to all the subscriptions for GPT-5.6 Sol. That should result in around 10% more usage on its own. - We noticed that by changing the context size limit in the product to 372k for GPT-5.6 Sol, up from 272k for GPT-5.5, it resulted in more usage being charged than intended. We have reverted to 272k and will work to roll back out to 372k in the days to come. You should notice that usage drains significantly less after this change. - To understand where the extra usage was coming from, we ran some experiments where reasoning efforts were changed (referred to as juice values under the hood) and have reverted this. - There is slightly more usage of multi-agent than intended in high and xhigh reasoning effort, we are fixing this going forward. Also fixing a small other thing we noticed with auto-review where we can be more efficient. And we continue to have the 5h limit temporarily not apply. Enjoy the rest of the weekend!

Tibo@thsottiaux

Updates for Codex and ChatGPT Work users. No nerfing, only good stuff! - We have landed inference optimizations and are passing down savings to all the subscriptions for GPT-5.6 Sol. That should result in around 10% more usage on its own. - We noticed that by changing the context size limit in the product to 372k for GPT-5.6 Sol, up from 272k for GPT-5.5, it resulted in more usage being charged than intended. We have reverted to 272k and will work to roll back out to 372k in the days to come. You should notice that usage drains significantly less after this change. - To understand where the extra usage was coming from, we ran some experiments where reasoning efforts were changed (referred to as juice values under the hood) and have reverted this. - There is slightly more usage of multi-agent than intended in high and xhigh reasoning effort, we are fixing this going forward. Also fixing a small other thing we noticed with auto-review where we can be more efficient. And we continue to have the 5h limit temporarily not apply. Enjoy the rest of the weekend!

Quoting @FixlationAI

OpenAI has reduced GPT-5.6 Sol's thinking budgets in an effort to make the model more efficient They essentially bumped everyone's reasoning down by 1... so if you were running Sol Extra High, you now have to set it to Max to get the same effort So we basically don't have Max reasoning anymore, how do you feel about these changes? 🤔

Quoting @Lentils80

🚨 GPT-5.6 Sol's juice values (thinking budgets) have been severely degraded compared to release day If Sol now feels faster and more "efficient", this is probably why Terra and Luna juice values aren't affected, so their thinking budgets are now higher than Sol's https://t.co/6Uf3iArPPu

Tibo@thsottiaux

Team, Edu, ... and any other paid subscription too. Quite simple really.

Reply to @thsottiaux

Rest assured that GPT 5.6 Sol will stay in the ChatGPT subscription you pay for. Including Go, Plus and Pro subscriptions. At least until we ship an even better model.

Tibo@thsottiaux

@_Mira___Mira_ Fair is fair

Reply to @_Mira___Mira_

I love the rate limit resets, but they have to know I'm going to start 11 Ultra threads to use the remaining 30% weekly allotment before it gets reset, when they announce it in advance like this.

Quoting @thsottiaux

Morning. The last 48 hours of Codex and ChatGPT Work have been intense! Three important updates: - Temporarily removing the 5 hour usage limit restriction for all Plus, Business and Pro plans - Rolling out changes that will make GPT 5.6 Sol more efficient across the board and that will be reflected in less usage being used so that it can take you further. Exact impact to be quantified and shared - We hit 6M active users, and are landing a usage reset in the next hour Go do things

Tibo@thsottiauxCredit announcement

Added a banked reset to 500k users of ChatGPT Work and Codex. What’s been happening: - Just released the ability to use a banked reset from web and mobile. Before today you could only do it in the desktop app - Had an issue where less than 10% of users who used a banked reset and it didn’t actually reset. This was during a 2 hour window. - It was hard to find all the exact users where it didn’t apply, so instead granted a banked reset to everyone who pressed the reset button in that 2 hour window. This also gives us the opportunity to validate the new infra ahead of tomorrow Tomorrow we will celebrate our 7M active users milestone and grant the first banked reset across all of our ChatGPT Work and Codex users. We will also release a bunch of updates to the desktop app, addressing a ton of your feedback. Talk soon

Tibo@thsottiaux

@mweinbach Yes

Reply to @mweinbach

@thsottiaux So what im hearing is I can GPT 5.6 Sol Ultra Fast my way through 3 banked resets in an afternoon

Reply to @thsottiaux

Morning. The last 48 hours of Codex and ChatGPT Work have been intense! Three important updates: - Temporarily removing the 5 hour usage limit restriction for all Plus, Business and Pro plans - Rolling out changes that will make GPT 5.6 Sol more efficient across the board and that will be reflected in less usage being used so that it can take you further. Exact impact to be quantified and shared - We hit 6M active users, and are landing a usage reset in the next hour Go do things

Tibo@thsottiauxAnnouncement

Morning. The last 48 hours of Codex and ChatGPT Work have been intense! Three important updates: - Temporarily removing the 5 hour usage limit restriction for all Plus, Business and Pro plans - Rolling out changes that will make GPT 5.6 Sol more efficient across the board and that will be reflected in less usage being used so that it can take you further. Exact impact to be quantified and shared - We hit 6M active users, and are landing a usage reset in the next hour Go do things

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?

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