@MaxForAI: Tibo Just Revealed the Origins of Codex's Reset Mechanism! Turns out, Codex often 'Resets' to give everyone credits, and this is the backstory. What's now nearly a Codex community tradition started as anything but a carefully designed marketing campaign. The initial logic was very...
Summary
Tibo revealed the origins of Codex's Reset mechanism: initially to compensate users for issues encountered during use, it later evolved into a community tradition and even features a physical button.
View Cached Full Text
Cached at: 08/25/26, 10:11 AM
Just now, Tibo explained the origin story of the Reset mechanism for the first time!
It turns out that Codex frequently “Resets” to give everyone usage quotas, and this is how it all started.
This practice, which has now almost become a tradition in the Codex community, began not as a meticulously planned operational activity.
The original logic was very straightforward:
Codex was iterating rapidly and often broke things.
It could be a misconfiguration, a service issue, or a period where the product experience clearly fell short of expectations.
@thsottiaux believed that since users spent their own quotas testing the product and the problems were caused by OpenAI, they should be compensated.
So initially, it was simply to compensate for breaking things—here’s some extra usage for you.
Over time, this gradually evolved into what we’re familiar with today: directly resetting usage limits.
Interestingly, this process has always been quite “makeshift.”
Tibo said that behind the reset, there was no complex approval process, nor was it a coordinated effort with Marketing or Finance.
He could even decide for himself when to press the button.
During the interview, the host compared it to Amazon’s return policy:
If it’s our fault, we’ll make it right.
Over time, users developed a strong expectation: this company genuinely cares about my experience.
This might also explain why such a simple and straightforward mechanism ended up becoming one of the most distinctive cultural elements of the Codex community.
And there’s an even more outrageous detail at the end of the video:
The host asked Tibo:
“I heard you’ve actually made a physical Reset Button?”
Tibo smiled:
“I can take you to see it.”
So all those “RESET” announcements Tibo posts daily on X? It’s quite possible he really walks over and presses a button by hand.
Similar Articles
@every: Thank goodness because guess who needs it...
Tibo announces that Codex has reached 20 million active users and credits every Codex and ChatGPT Work user with a BANKED reset as a celebration.
@xiaogaifun: A Major Pitfall Our Team Encountered with Codex. I want to sincerely share a topic we discussed in our weekly meeting. This might be a common pitfall for many people using agent products like Codex. In short, if we just keep issuing commands and accepting suggestions from Codex without understanding or judgment, then these...
The team shares the problem of over-reliance on AI leading to a lack of deep understanding among members when using Codex. It emphasizes that humans should act as leaders of AI, not mere messengers, and need to understand the principles and logic, turning AI output into their own experience.
@reach_vb: PSA: The button has been pressed! All of you should be seeing a reset in your accounts in the coming hours. Let the cod…
The reset button has been pressed for Codex subscribers at the AIE World's Fair, resetting all accounts for Codex Go/Plus/Pro users.
Codex is down, excited for my reset
The AI model Codex is experiencing an outage, and the author is eagerly awaiting its reset.
@Luckyjudy666: 8 Tips to Make Codex Your Personal Assistant 1. Build a Shared Memory for Codex Core rules go in Agents.md, project background in Obsidian, repeated processes as skills, personal preferences and common questions in Memories. Otherwise, Codex is like a new colleague every time, having to explain everything from scratch...
This article shares 8 tips for using the Codex AI assistant effectively, including building shared memory, remote task execution, scheduled automation, file organization, and teaching new software operations, all aimed at improving work efficiency.