Codex 28 · Day record · 19 Oct 2026

Day 15 of 28

Closed at 00:00 UTC on 20 Oct 2026 Counted only from activity timestamped inside this UTC day. Later votes, answers and experiences do not change it; only an entry in the corrections log can.

Revised 25 Oct 2026, 06:40 UTC after an entry in the corrections log. Corrections log →

Download card

The day’s change

Recorded update

Improvement

Day 15: Tibo points to OpenAI's COOKED Codex broadcast

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.

Source ↗

Fewer than 10 votes by the close of the day; the tally is in the open data, not shown here.

Reset

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

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.

Source ↗

Recorded after the day closed (20 Oct 2026, 06:53 UTC), so no votes fall inside the day.

Fewer than 10 votes by the close of the day; the tally is in the open data, not shown here.

Running totals

What changed since day 14

Totals since 5 Oct 2026, at the close of each day; today’s are so far. A total never goes down when a sample is recounted.

Experiences

Experiences published this day

1 problem

Threads

Most mentioned experience threads

A mention is an experience published in a thread or a “Same here” given this day. Mentions this day in all: 1.

  1. A problem
    Sol keeps spawning agents in Ultra mode, and it's burning through my tokens like crazy.

    1 of 1 mentions this day · in the thread so far: experiences 1, “Same here” 0

Replies on X

Replies to Tibo’s post published this day

A sample collected from X, not every reply. Each link opens the reply on X.

Replies dated this day in the collected sample: 97. Collected since 5 Oct 2026: 2080.

X replies are found by search and each one is checked against its public post on X. Last read: 26 Oct 2026, 23:46 UTC. Not every reply is read.

2 X replies from this day are not quoted: Rantr does not have their words or held them back after automated screening. They stay on X.

Corrections log

Corrections logged this day

  1. · Update

    Day 14: Tibo announces editing previous messages within a thread in the Codex desktop app

    Before
    The Day 14 entry said the post does not say how editing an earlier message affects the rest of the thread.
    After
    Added Tibo's follow-up that an edit "registers as time travel", not as a steer; what happens to later messages, actions and usage is still unspecified, and Rantr has not independently verified.
    Why
    Tibo followed up on X: https://x.com/thsottiaux/status/2111994295364571327

Nothing this day for: OpenAI release notes.

Method

How this record is made

Each day runs from 00:00 to 24:00 UTC. The record counts votes, release check answers, experiences, “Same here” and replies timestamped inside the day. When the day closes the record is frozen; it is recomputed only after an entry in the public corrections log, or when the day’s update is recorded late. Rantr is a neutral record: it does not take a side.

Corrections log → Open data and method →