X：Kim

What I wanted to say yesterday is that we hit 25M active users and to celebrate we have now reset usage for all paid subscriptions for ChatGPT Work and Codex. See you soon for more news from The Reset Company. https://t.co/7Yc5znAJIc

Down the rabbit-hole it gets worse and worse. Anthropic’s “Save 50%” claim makes even less sense than I thought. The label suggests that the $200 Max 20x plan gives you four times the usage of the $100 Max 5x plan for only twice the price. We already figurer that out. But Anthropic’s own website disclosed very different weekly limits in 2025: Max 5x: 140–280 hours of Sonnet per week Max 20x: 240–480 hours of Sonnet per week That is only around 1.7x more weekly usage, not 4x, despite costing twice as much. So once you hit the weekly limit, you are not saving 50%. You are effectively paying more per expected hour of usage. Save 50% doesnt make any sense at all.

Imagine celebrating that ChatGPT Search has become huge in Europe because it means you can finally regulate it. And no, this isn't a parody account from the EU Commission. They’re serious. ChatGPT Search now reaches 159 million monthly users in the EU. Europe has failed to build anything remotely comparable. So the European Commission proudly announces that ChatGPT is now large enough to face even more regulation. This image perfectly captures European AI policy. If any of you have ever read Franz Kafka’s *The Trial*: this goes far beyond that.

I went down the rabbit hole: Anthropic is already being sued over exactly this. And the $200 plan really only provides only around 2x the weekly usage of the $100 plan Here is where the confusion comes from. Anthropic’s pricing page says: “Choose 5x or 20x more usage than Pro.” That naturally makes the $200 Max 20x plan sound like it includes four times the usage of the $100 Max 5x plan. Only further down does Anthropic clarify: “Max gives you 5x or 20x more usage per 5-hour session than Pro.” Those multipliers do not apply to the separate weekly caps, whose exact size Anthropic does not disclose. A proposed class action filed in June alleges that Max 5x delivers around 3.5x Pro’s weekly usage, while Max 20x delivers just 6–8x. In practice, the $200 plan therefore provides only around 2x the weekly usage of the $100 plan, sometimes even less depending on the model. The “20x” is real within each five-hour window. The weekly limit makes the overall offer look very different. h/t @Hesamation for finding the original court files first i think

Today I learned : Claude’s $200 Max plan offers 20x Pro usage within the five-hour window, but its weekly limit is only about twice that of the $100 plan. Oh and btw: Tibo has confirmed that Codex really sees 5x more weekly usage. Anthropic strikes again https://t.co/qM7Q9EsyJ0

For clarity, while both are called 20X, in Codex they apply specifically to weekly usage limits. And we also don't have 5h limits for both Pro plans. The Pro 20X is quite precisely 20X the usage of the Plus subscription, so it does exactly what it says on the tin. https://t.co/vMchMCT80Z

Your Codex and ChatGPT Work reset will land at 6pm PST. I challenge you to burn as much usage as you can and discover and the latest awesome features. Time to go /fast

This celebration is moved to tomorrow as the button was already pressed today. https://t.co/lAywb9TV44

This celebration is moved to tomorrow as the button was already pressed today. https://t.co/lAywb9TV44

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!