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@thsottiauxConfirmed

@0xrsydn Omg omg omg, back to 100%!

Reply to @0xrsydn

HOLYSHIT I WAS AT AROUND 10% WEEKLY USAGE LEFT OMG

Quoting @thsottiaux

Hello people of Sol! I've reset usage limits for all ChatGPT Work and Codex users. Together with that, a quick update on GPT-5.6 Sol usage limits. Over the past few weeks, many of you have told us that Sol was using your Codex limits faster than expected. To be clear, we have not reduced usage on any subscription plans. We’ve been digging into what was happening and have landed several improvements. As a result, we expect your usage to last around 18% longer during typical use of Sol. Some of you should already see significantly larger improvements from today. Tomorrow, we’ll also restore the five-hour limit that we temporarily paused while investigating. Here’s what we found: - GPT-5.6 Sol is much more willing to work for longer, make additional tool calls, and coordinate complex workflows across tools and subagents. That makes it better at solving hard problems, but some tasks were using far more than we intended. - Sol also works harder at the same reasoning effort than previous models. High on Sol can use more tokens than High did on GPT-5.5. - Programmatic tool calling, also referred to as code mode, gives Sol much more flexibility to run tool calls in parallel or continue working while waiting. But it also led to more responses per turn, more cached input tokens, and higher usage than expected. - This was particularly noticeable when Sol was waiting for tool calls to finish or running many web searches. We’ve improved how we handle both cases and are continuing to make code mode more efficient. - The impact was also very uneven. The median user actually found Sol quite token efficient, while some power users working on harder tasks saw their usage drain much faster. We were very focused on average and median usage before launch and missed some cases where the long tail could use significantly more usage. Sol is a significant step forward in what Codex can do, but capability and efficiency do not always improve at the same pace, and some issues only become clear once people are using the model at real-world scale. We should have recognized this sooner and been more upfront about it. You keep pushing the frontier and we’ll keep improving efficiency and sharing updates as we go.

Tibo@thsottiaux

@justindico And yet

Reply to @justindico

He can't keep getting away with this! I haven't even burned 50% since the last reset.

Quoting @thsottiaux

Hello people of Sol! I've reset usage limits for all ChatGPT Work and Codex users. Together with that, a quick update on GPT-5.6 Sol usage limits. Over the past few weeks, many of you have told us that Sol was using your Codex limits faster than expected. To be clear, we have not reduced usage on any subscription plans. We’ve been digging into what was happening and have landed several improvements. As a result, we expect your usage to last around 18% longer during typical use of Sol. Some of you should already see significantly larger improvements from today. Tomorrow, we’ll also restore the five-hour limit that we temporarily paused while investigating. Here’s what we found: - GPT-5.6 Sol is much more willing to work for longer, make additional tool calls, and coordinate complex workflows across tools and subagents. That makes it better at solving hard problems, but some tasks were using far more than we intended. - Sol also works harder at the same reasoning effort than previous models. High on Sol can use more tokens than High did on GPT-5.5. - Programmatic tool calling, also referred to as code mode, gives Sol much more flexibility to run tool calls in parallel or continue working while waiting. But it also led to more responses per turn, more cached input tokens, and higher usage than expected. - This was particularly noticeable when Sol was waiting for tool calls to finish or running many web searches. We’ve improved how we handle both cases and are continuing to make code mode more efficient. - The impact was also very uneven. The median user actually found Sol quite token efficient, while some power users working on harder tasks saw their usage drain much faster. We were very focused on average and median usage before launch and missed some cases where the long tail could use significantly more usage. Sol is a significant step forward in what Codex can do, but capability and efficiency do not always improve at the same pace, and some issues only become clear once people are using the model at real-world scale. We should have recognized this sooner and been more upfront about it. You keep pushing the frontier and we’ll keep improving efficiency and sharing updates as we go.

Tibo@thsottiauxConfirmed

Hello people of Sol! I've reset usage limits for all ChatGPT Work and Codex users. Together with that, a quick update on GPT-5.6 Sol usage limits. Over the past few weeks, many of you have told us that Sol was using your Codex limits faster than expected. To be clear, we have not reduced usage on any subscription plans. We’ve been digging into what was happening and have landed several improvements. As a result, we expect your usage to last around 18% longer during typical use of Sol. Some of you should already see significantly larger improvements from today. Tomorrow, we’ll also restore the five-hour limit that we temporarily paused while investigating. Here’s what we found: - GPT-5.6 Sol is much more willing to work for longer, make additional tool calls, and coordinate complex workflows across tools and subagents. That makes it better at solving hard problems, but some tasks were using far more than we intended. - Sol also works harder at the same reasoning effort than previous models. High on Sol can use more tokens than High did on GPT-5.5. - Programmatic tool calling, also referred to as code mode, gives Sol much more flexibility to run tool calls in parallel or continue working while waiting. But it also led to more responses per turn, more cached input tokens, and higher usage than expected. - This was particularly noticeable when Sol was waiting for tool calls to finish or running many web searches. We’ve improved how we handle both cases and are continuing to make code mode more efficient. - The impact was also very uneven. The median user actually found Sol quite token efficient, while some power users working on harder tasks saw their usage drain much faster. We were very focused on average and median usage before launch and missed some cases where the long tail could use significantly more usage. Sol is a significant step forward in what Codex can do, but capability and efficiency do not always improve at the same pace, and some issues only become clear once people are using the model at real-world scale. We should have recognized this sooner and been more upfront about it. You keep pushing the frontier and we’ll keep improving efficiency and sharing updates as we go.

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