Recent Codex Reset Events

Note

A regular reset occurs one week after you first use Codex or Work following the previous reset. If you use a Banked Reset, the next weekly timing is likewise counted from your first use after that reset, so it may differ from the time shown here.

Note

As Day 2 of the two-day announcement following the mobile account switching release, a second distribution of a BANKED Reset was confirmed.

Note

Following the release of mobile account switching, the first distribution of a BANKED Reset was confirmed.

Note

Tibo mentioned the much-requested iCloud Main and Calendar plugins, clarified that this was a joke, and announced a reset. The post did not announce new plugins. Codex weekly usage limits later recovered.

Note

On Day 21 of the daily improvements-and-resets series, Tibo wrote, “Wonder what happens the remaining seven days. But today is a reset.” The monitor subsequently confirmed that Codex weekly usage limits had recovered. The post did not specify what the remaining days would bring.

Note

Tibo announced “Rest and reset” and supplied the deadline in a follow-up reply. He later reported that propagation was complete, encouraging Codex use and expressing enthusiasm for what comes next.

Note

Tibo rounded up the Decisions API’s general availability, OpenResponses joining the Linux Foundation, performance improvements, and Uber’s adoption of Codex and Work, then added “But yes… that’s a reset!” A follow-up reply gave the deadline, and Codex weekly usage limits were restored after the announcement.

Note

Tibo wrote, “Bet you thought we forgot, but no, it’s reset day today.” A follow-up reply gave the deadline, and Codex weekly usage limits were restored after the announcement.

Note

Tibo turns the earlier “We’re cooked” into “we’re still cooking,” a cooking-related wordplay reversal. He then confirms the reset, restoring available Codex usage.

Note

Tibo announced this Codex usage-limit reset with “Day 13/ Le limit reset.” It directly refreshed usage limits to restore available capacity, and he confirmed completion in a follow-up post saying “Done.”

Note

Tibo joked that reports of his reset button being lost were greatly exaggerated and announced a reset for Day 10. A follow-up said it would land within two hours, and the completion post came about one hour and 32 minutes after the original notice. This reset directly refreshed Codex usage limits to restore available capacity.

Note

Tibo announced that the reset was done with a playful question likening it to a side dish. The completion post came about four hours after the global-reset notice. This reset directly refreshed Codex usage limits.

Note

A BANKED Reset distribution was observed.

Note

A BANKED Reset distribution marking the GPT-6.1 release was observed.

Note

A BANKED Reset distribution was observed.

Note

In response to quality issues, usage limits for Codex and ChatGPT Work were forcibly reset.

Note

An issue occurred where some Banked Resets did not fully apply when used in ChatGPT Work and Codex. Users who used one during the affected time window are receiving an apology email along with a replacement Banked Reset.

Note

The reset was carried out sequentially rather than simultaneously for all accounts, so the execution time varied by account.

Note

To mark the GPT-6 Astra launch, a BANKED Reset was distributed. Distribution may take place progressively rather than all at once.

Note

To mark the GPT-6 Astra launch, a BANKED Reset was distributed. Distribution may take place progressively rather than all at once.

Note

Codex weekly usage limits were confirmed to have been reset.

Note

Codex weekly usage limits were confirmed to have been reset.

Note

Tibo announced that Codex usage limits were reset.

Note

Codex usage limits were reset as compensation for the weekend's excessive consumption issue.

Note

A BANKED Reset distribution was observed.

Note

A regular reset occurs one week after you first use Codex or Work following the previous reset. If you use a Banked Reset, the next weekly timing is likewise counted from your first use after that reset, so it may differ from the time shown here.

Note

To celebrate Codex surpassing 15 million active users, usage limits for ChatGPT Work and Codex were forcibly reset.

Note

A regular reset occurs one week after you first use Codex or Work following the previous reset. If you use a Banked Reset, the next weekly timing is likewise counted from your first use after that reset, so it may differ from the time shown here.

Note

Tibo announced a forced reset for all Codex and ChatGPT Work users to celebrate a week of efficiency gains and enable 100,000 Luna threads over the weekend.

Note

Following the announcement by Tibo regarding efficiency improvements for the GPT-5.6 Sol model (~18% longer usage duration), rate limits for all ChatGPT Work and Codex users were forcibly reset immediately.

Note

Usage limits for Codex and ChatGPT Work were forcibly reset to celebrate the rapid adoption of ChatGPT Work and team efforts.

Note

Usage limits for ChatGPT Work and Codex were forcibly reset following full recovery from a global system outage.

Note

Usage limits for ChatGPT Work and Codex were reset to celebrate reaching 10 million active users.

Note

Usage limits for ChatGPT Work and Codex were reset for a fourth time following additional investigations and improvements to GPT-5.6 Sol.

Note

Usage limits for ChatGPT Work and Codex were reset to celebrate reaching 9 million active users.

Note

Usage limits for ChatGPT Work and Codex were reset to celebrate reaching 8 million active users.

Note

One Banked Reset was granted to all paid users (Codex Go/Plus/Pro) to celebrate reaching 7 million active users.

Note

One Banked Reset was granted as compensation to approximately 500,000 affected users whose reset did not apply after they pressed the button during the web/mobile feature rollout.

Note

Usage limits for ChatGPT Work and Codex were reset to celebrate reaching 6 million active users.

Note

Usage limits for ChatGPT Work and Codex were reset for a third time to celebrate the GPT-5.6 Sol launch.

Note

Usage limits for ChatGPT Work and Codex were reset for a second time to celebrate the GPT-5.6 Sol launch.

Note

Codex usage limits for all paid plans were reset to celebrate the GPT-5.6 launch.

Note

A regular reset occurs one week after you first use Codex or Work following the previous reset. If you use a Banked Reset, the next weekly timing is likewise counted from your first use after that reset, so it may differ from the time shown here.

Note

During the AI Engineer World's Fair demo, the Codex reset button was pressed, granting one Banked Reset to all paid users (Codex Go/Plus/Pro).

Note

Tibo announced that a full reset would take place within an hour. Codex limits were then reset for all users as compensation for an excessive-usage issue.

Note

Due to an issue causing excessive usage limit consumption for some users, everyone's Codex limits were forcibly reset (cleared) during the investigation.

Note

One Banked Reset was distributed to all paid plans as compensation for model degradation and excessive usage consumption issues.

Note

A regular reset occurs one week after you first use Codex or Work following the previous reset. If you use a Banked Reset, the next weekly timing is likewise counted from your first use after that reset, so it may differ from the time shown here.

Note

A regular reset occurs one week after you first use Codex or Work following the previous reset. If you use a Banked Reset, the next weekly timing is likewise counted from your first use after that reset, so it may differ from the time shown here.

Note

One Banked Reset was distributed to all accounts as compensation for issues affecting Codex reliability.

Note

This was not a regular forced reset. One Banked Reset was distributed, and the resulting usage window or next date may differ by account.

Note

As compensation for three incidents affecting Codex reliability in the past 24 hours, usage limits for all paid plans were reset.

Note

To celebrate reaching 5 million active Codex users, usage counts for all paid ChatGPT/Codex users were forcibly reset.

Note

After a bug causing excessive consumption due to lower cache-hit rates in Codex long-session compression was fixed, all paid users' limits were reset.

Note

After Sam Altman's tweet reached one like, Tibo immediately reset the Codex usage limit.

Note

Following the resolution of a temporary GPT-5.5 performance-degradation issue, usage counts for all paid plans were forcibly reset.