# Page 4 - Codex reset history

Codex reset announcement history: dates, reset types, publishers and evidence links. Unofficial and advisory only.

Language: en
Time zone: America/Los_Angeles
Current time (UTC, cached as of): 2026-11-10T06:50:00.000Z
Query date (America/Los_Angeles): 2026-11-09

HTML: https://didcodexreset.com/history-page-4.html

Reset record: 59 Codex resets recorded between 9/16/2025 and 10/27/2026 · median gap 3.5 days · longest gap 67.7 days

## 2026-08-11

### Completed reset; Global Reset; announced 8/10/2026, 17:27:44 (America/Los_Angeles).

> Hi.
>
> It is done.

[Details](https://didcodexreset.com/history/1786408064000.html)

## 2026-08-08

### Completed reset; Global Reset; announced 8/8/2026, 13:29:22 (America/Los_Angeles).

> That's right, GPT-5.6 Sol is awesome and can be used pretty much anywhere, including in the CC harness. 
>
> To celebrate this, together with the fact that I'm not going anywhere... I have reset usage limits for all paid users of ChatGPT Work and Codex. 
>
> Have fun out there!

[Details](https://didcodexreset.com/history/1786220962000.html)

## 2026-08-01

### Completed reset; Global Reset; announced 7/31/2026, 20:32:37 (America/Los_Angeles).

> To celebrate a week of efficiency and let you run 100'000 Luna threads this weekend... that's right... wait for it... I have reset usage limits for Codex and ChatGPT Work.
>
> Enjoy.

[Details](https://didcodexreset.com/history/1785555157000.html)

## 2026-07-29

### Completed reset; Global Reset; announced 7/28/2026, 22:42:35 (America/Los_Angeles).

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

[Details](https://didcodexreset.com/history/1785303755000.html)

### Completed reset; Global Reset; announced 7/28/2026, 21:09:02 (America/Los_Angeles).

> 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.

[Details](https://didcodexreset.com/history/1785298142000.html)

## 2026-07-28

### Completed reset; Global Reset; announced 7/27/2026, 20:09:23 (America/Los_Angeles).

> Back at the laptop. The usage limits have been reset for all paid users of Codex and ChatGPT Work. Weeeeeeeee. It's a good day!

[Details](https://didcodexreset.com/history/1785208163000.html)

## 2026-07-25

### Completed reset; Global Reset; announced 7/25/2026, 12:17:12 (America/Los_Angeles).

> We have reset usage limits for all Codex and ChatGPT Work users.
>
> Last night around 2am to 4am we suffered an almost global outage. All well and recovered, but you know what comes next.
>
> We learn. We reset. Enjoy.

[Details](https://didcodexreset.com/history/1785007032000.html)

## 2026-07-21

### Completed reset; Global Reset; announced 7/21/2026, 09:47:15 (America/Los_Angeles).

> 10M! 
>
> New day, new usage reset for paid users of Codex and ChatGPT Work. Lands in the next hour. Enjoy.

[Details](https://didcodexreset.com/history/1784652435000.html)

## 2026-07-18

### Completed reset; Global Reset; announced 7/17/2026, 20:28:22 (America/Los_Angeles).

> Oops... I did it again. 
>
> Enjoy reset usage limits for all paid users for Codex and ChatGPT Work. Super grateful for an incredible team who is iterating at lightspeed and keeping the infra up as we scale faster than ever.
>
> Enjoy the weekend!

[Details](https://didcodexreset.com/history/1784345302000.html)

## 2026-07-16

### Completed reset; Global Reset; announced 7/15/2026, 21:14:09 (America/Los_Angeles).

> Another reset for our Codex and ChatGPT Work users. Actually hit 9M active users way earlier today, but then got distracted by the approximately millions of things the team is doing to keep the systems up and reliable.
>
> Should have that sweet 100% weekly usage limit back in a few minutes. Go be your productive self and close twitter. Shoo!

[Details](https://didcodexreset.com/history/1784175249000.html)

[Previous page](/history-page-3.html.md) · [Next page](/history-page-5.html.md)
