Day 23 of 2822:29:25left to ship today

What did Codex do to you today?

Tibo promised a real improvement or a full reset every day for 28 days. Say what Codex did to you, and see whether any day answers it.

One sentence. No account.

0 / 1200

Tell us a little more — at least 20 characters.

Your words stay yours.

AI reads your draft as you type. Only what you publish is public. Privacy

Not sure where to start?

Think of the last task you tried. What were you doing, what happened, and what would have helped? You can also say you haven't tried a change yet.

  1. What you said

    Read as you type: a win, a problem or an idea, and the words that carry it.

    Ready when you are

  2. Who else had it

    The theme your words join, and how many people on Rantr and X described it.

  3. Where OpenAI stands

    Shipped, reset, or not addressed yet, from the recorded announcements.

  4. What to do now

    A step the announcements make possible for you, when there is one.

The 28-day promise

Tibo’s 28-day Codex promise, recorded day by day.

Tibo promised a meaningful improvement for most Codex/Work users, or a full reset, every day for 28 days.

Tibo · @thsottiaux · 4 Oct 2026 ↗

Rantr is an independent, open record of what was promised, what shipped and what users say. Wins and problems are shown equally.

5 Oct 2026 – 1 Nov 2026 · UTC · Independent scorecard. Not affiliated with OpenAI or Tibo.

In their own words

What worked for others

Things Codex users on X say they did that helped. Each is one person’s report; Rantr has not tested it.

Day 15 · 19 Oct 2026

What Tibo shipped

22 of 22 days kept · day 23 open

15Tibo announces a reset after saying "we're still cooking"Full reset

Tibo's post reads, in full: "Day 15/ Nevermind, we're still cooking... and reset. Enjoy." It quotes his earlier Day 15 post, "Day 15/ We're cooked", which pointed to OpenAI's COOKED Codex broadcast. It was published on 20 October at 06:33 UTC, after Day 15 ended in UTC; he explicitly names Day 15, so it is recorded as that day's reset rather than Day 16.

Read the whole note

This is a usage reset as Tibo announces it, not a lasting change to the limits themselves and no model or speed improvement. The post does not say which plans receive it, whether it is applied automatically or banked for later, when it lands, or whether anything expires.

Check your usage panel for a refreshed balance or a banked reset and any expiry. Rantr has not independently verified the reset or its application to individual accounts.

Check the source ↗

Replies to this announcement
15Tibo points to OpenAI's COOKED Codex broadcastImprovement

Tibo labels his post "Day 15/ We're cooked" and quotes OpenAI Developers' post, "Here’s what we’re cooking with Codex:", linking to the broadcast "COOKED: Ep. 1". Official source ↗

Read the whole note

The post and quoted text do not name a specific shipped feature, rollout scope, availability date or measured improvement, and do not announce a usage reset. This entry records his Day 15 pointer to the broadcast; it does not establish that a concrete improvement has shipped or that any recorded complaint has been resolved.

The linked broadcast is at x.com ↗. Rantr has not independently verified any product changes demonstrated or discussed in the broadcast; this entry is based on the post and quoted text, not a review of the video.

Check the source ↗

Replies to this announcement

Announcements are context. Your experience tells us what they actually changed.

Open the day 15 record →

02 → 04 · Who had it, the step, the status

What people describe, and where each one stands

Themes are what people describe, grouped by AI from Rantr experiences and collected X replies. Each one shows how many had it, what to do now, and whether an announcement answered it. AI groups; it does not verify claims.

Loading themes…

    See every theme →

    X thread: replies are found by search and each one is checked against its public post on X. X figures count only the replies read.

    Read every collected reply to the promise

    Community feedback

    No experiences yet. Yours would be the first.

    OpenAI release notes

    What OpenAI published for this day. Answers about a note are counted apart from the vote on the day’s change.

    Loading release notes…

    OpenAI’s full changelog ↗
    How this campaign works

    Writing is the contribution: you tell, in your own words, what the day’s changes did for you. AI groups related experiences into themes; a group shows experiences that resemble each other, not verified claims or representative polling. A theme’s status comes from AI linking a recorded announcement to it; the what-to-do line is written only from that announcement’s own words and checked against it before it is shown.

    Rantr records source-linked updates; the community judges their usefulness. Our tracking window is 5 October–1 November 2026, using UTC days. The original post does not specify a timezone. Improvements and resets are counted separately, and a day can include both.

    Historical votes (before input-only feedback)

    One editable vote per update per browser, stored on Rantr. A 90-day essential cookie remembers this browser. Anonymous voting is not a verified-person poll. “Not tried” never affects the usefulness percentage. No fabricated votes or automatic failure verdicts.

    Votes · Self-selected browser votes, not verified people or a representative survey. X replies do not enter this percentage. The crowd agrees with a day when its Useful votes outnumber its Not enough votes. Day records show a vote tally only once an update has 10 votes or more; smaller tallies stay in the open data.

    What these numbers can tell you

    Theme status · “Shipped” means an announcement was linked to the theme by AI, not that the problem is fixed for everyone. “Not addressed yet” means no recorded announcement was linked; it is not proof that nothing changed.

    Recorded days · A day is kept when an improvement or a full reset is recorded.

    Sources · Announcements, X replies and Rantr votes are separate sources. Votes are self-selected browser responses, not a representative survey. JEV identifies themes; it does not verify whether an experience happened. Read the original sources and compare both positive and negative experiences. X evidence covers only the replies Rantr has read: found by search, each one checked against its public post on X. It shows when they were read and how many. A reply not read is not a reply that does not exist. Imported replies never count as votes.

    Release notes · Publication dates are not proof of availability for every account. Release notes do not automatically mark a campaign day as kept.

    Community feedback · Related experiences are grouped automatically. Connections may be imperfect; they do not prove a fix. One experience per browser per day. “Same here” counts browsers, not verified people.

    X replies · Replies to the original conversation. These do not judge a shipped feature or count as votes.

    About Rantr. Rantr is where people say what a product did to them, anonymously, and see who feels it too. When the same thing keeps coming up, the pattern becomes visible to everyone, its makers included. Go to Rantr →