No occasion · Codex · Hard reset
Oops, he did it again — a Friday-night flush with a thank-you attached
No incident named, no milestone claimed. Reset usage limits for all paid Codex and ChatGPT Work users, and credit to a team keeping the infrastructure up.
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! https://t.co/WIuS07doKA
“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.”
Four days after the 8 million toast, with nothing broken, the button went again. Oops, said Tibo, I did it again. Then a thank-you to the team keeping the infrastructure standing while the product scaled faster than ever, and a wish for the weekend.
The self-aware bit is the point. By mid-July the author of these posts knew the reset had become a genre with an audience, and he started writing to it. That is when a maintenance action turns into a beat.
We file the scope exactly as written — all paid users for Codex and ChatGPT Work — and nothing else, because nothing else is stated. The gratitude is real and it is not a scope.
What it means
- Paid scope, both products. The only stated reason is scale and gratitude.
- Posted 03:28 UTC — Friday evening in San Francisco, which is what the closing line about the weekend is measuring.
- Oops is a joke about frequency. The desk had flushed on the 14th and would flush again on the 21st and the 25th.