Double flush · Codex · Hard reset
Two in one day: Tibo resets Codex, then promises another before dark
The only post on file that pre-announces a second flush the same day — and then uses the attention it bought to publish a product update.
Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice. Now that I have your attention, a quick update on ChatGPT Work, Codex and all the updates we shared yesterday. We’ve spent the last 24 hours
Post continues · read the rest on X
“Hello beautiful people! We have reset usage limits across Codex and ChatGPT Work. And another one will come later in the day. Rejoice.”
On the Friday after the ChatGPT Work updates, the Codex desk opened with hello beautiful people, announced that usage limits had been reset across both products, and then said another one would come later in the day. Rejoice, he wrote, and then admitted the reset was partly a megaphone.
The next line is the honest one: now that I have your attention, a quick update on ChatGPT Work, Codex and the updates shared the previous day, after twenty-four hours of work. The flush is real and the flush is also a headline generator, and the post says so in its own copy.
We file the confirmed reset and leave the second one where he left it — as a promise made at 17:59 UTC, not as a second card. If the evening flush had its own post, it is not in this drawer.
What it means
- Two resets are described: one already applied, one promised for later the same day. Only the first is confirmed in this post.
- Scope is stated as across Codex and ChatGPT Work, with no paid qualifier in the sentence. We copy it as written rather than tidying it.
- If you are counting flushes for a cadence chart, decide now whether a promised second reset counts as an event. We count the post, not the promise.