Codex 28 · Day record · 21 Oct 2026

Day 17 of 28

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

The day’s change

Recorded update

Reset

Day 17: Tibo announces a reset as the Day 17 delivery

Tibo writes: "Day 17/ Bet you thought we forgot, but no, it's reset day today." In the same post he reminds people to get "Daybreak Blue access, it only takes 15 mins and you don't want to have to do it in the middle of an incident." It was published on 22 October at 06:55 UTC, after Day 17 ended in UTC; he explicitly names Day 17, so it is recorded as that day's delivery rather than Day 18.

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. The Daybreak Blue reminder is not part of the reset, and the post does not explain what it is.

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.

Follow-up from Tibo on 22 Oct (x.com ↗): replying under the Day 17 post, he writes "Lands tomorrow before 10am PST.", so the reset announced for Day 17 is due to arrive on 23 October, before 10:00 Pacific time (17:00 UTC under the daylight time in effect that day; 18:00 UTC if read literally as standard time). Scope: it gives the timing only; it still does not say which plans receive the reset, whether it is applied automatically or banked, or whether anything expires. Rantr has not independently verified.

Recorded after the day closed (22 Oct 2026, 07:03 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 16

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
    Codex Remote Control is broken when using VPN/proxy on macOS I’m using Codex on macOS with a VPN/proxy (such as Clash or Surge). Regular Codex functionality works, but Remote Control fails to enable, displaying errors including “Couldn’t update remote control availability” and “Could not enable remote control.” I tried changing proxy settings and troubleshooting from Terminal, but the problem persisted. One configuration change even prevented Codex from launching, so I had to revert it. Please ensure that Remote Control and all its background processes correctly respect macOS system proxy settings, including HTTP(S)/SOCKS proxies, TUN mode, and WebSocket connections. Remote Control should work reliably behind a VPN without requiring manual environment-variable workarounds. Please also provide meaningful connection diagnostics rather than generic errors. This is particularly important for users on networks where direct connections to OpenAI services are unavailable.

    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: 91. Collected since 5 Oct 2026: 2305.

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.

4 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.

Nothing this day for: OpenAI release notes, corrections.

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 →