Codex 28 · Day record · 23 Oct 2026

Day 19 of 28

Closed at 00:00 UTC on 24 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, 20:40 UTC after an entry in the corrections log. Corrections log →

Download card

The day’s change

Recorded update

Improvement

Day 19: Tibo announces faster call connection in dots, reasoning changes that keep the cache in Codex and Work, and a Codex CLI update

Tibo writes: "Day 19/ Small updates. Calls connect much faster for dots, changing reasoning in codex & work mid conversation does not invalidate cache anymore and a we've also updated the codex cli." It was posted at 23:12 UTC on 23 October, within Day 19.

Read the whole note

These are three small product changes, not a usage reset and not a change to the stated plan limits. The cache item follows the Day 12 and Day 16.2 caching updates: by Tibo's account, switching the reasoning setting partway through a Codex or Work conversation no longer forces its context to be re-read at the full input rate, which could make an allowance last longer for people who change reasoning often; the post gives no measured effect. Faster call connection applies to dots, not to Codex runs, and no timings are given. The post does not say which plans get each change.

To check the cache change, switch reasoning mid-conversation in Codex or Work and compare the usage it consumes before and after. Rantr has not independently verified these changes.

Follow-up from Tibo on 24 Oct (x.com ↗): on the Codex CLI update he says it adds reusable prompt presets, inline model and permission settings and enterprise MCP sign-in, fixes failures when resuming long sessions, and adds Windows corporate-proxy authentication; he also says CLI usage has grown 2X since DevDay. Scope: these are Codex CLI features and fixes, not a usage reset or a change to plan limits; the reply gives no version number or release notes link, and the 2X growth is his figure. Rantr has not independently verified.

Source ↗

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 18

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.

Release notes

OpenAI release notes published this day

Release check: is this better for you?

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: 135. Collected since 5 Oct 2026: 2547.

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.

1 X reply from this day is not quoted: Rantr does not have its words or held them back after automated screening. It stays on X.

Corrections log

Corrections logged this day

  1. · Update

    Day 19: Tibo announces faster call connection in dots, reasoning changes that keep the cache in Codex and Work, and a Codex CLI update

    Before
    The Day 19 update said only that Tibo had updated the Codex CLI, with no detail.
    After
    Tibo lists the CLI changes: prompt presets, inline model and permission settings, enterprise MCP sign-in, long-session resume fixes, Windows corporate-proxy auth.
    Why
    Tibo followed up on X: https://x.com/thsottiaux/status/2113770862860222611

  2. · Update

    Day 18: Tibo announces a reset, alongside Decisions API GA and unspecified performance improvements

    Before
    The Day 18 reset was announced with no word on when it lands.
    After
    Tibo added that it lands before 10am Pacific (morning of 23 Oct) together with a small ship.
    Why
    Tibo followed up on X: https://x.com/thsottiaux/status/2113492502355562875

Nothing this day for: published experiences.

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 →