ConfirmedcodexCodex users; exact plan exclusions were not stated.

Codex users received an immediate and banked double reset

Tibo confirmed a full Codex reset plus an additional banked reset that users could apply later.

Observed
First-party announcement
Time basis
The source confirms the reset was triggered or already done by this time; exact account propagation was not published.
Event type
global reset
Evidence level
first party
User action
Use this as sourced historical context; check the current in-product usage display for your own account.

ResetWire analysis

What this record adds

Why this reset happened

Tibo described a deliberate “double reset” but did not cite an outage, billing error or capacity failure as the reason in the verified source excerpt.

Who was affected

The post addressed Codex users without spelling out plan exclusions. It granted an immediate refill plus a separate banked reset that each user could apply later.

How precise is the timing?

The immediate reset is anchored to the announcement time. The banked credit is recorded as part of the same announcement, not as evidence that each user redeemed it then.

Why this record matters

This event matters because it separates two mechanisms that are often conflated: an automatic reset that applies now and a saved reset controlled by the user later.

Evidence

Attached sources

  1. Tibo SottiauxX · x postRetrieval: available

    We did a sneaky double reset. Not only do you get a full reset on us. But you are also getting one into the reset bank.

    Read the original source →
    Optional official embed · third-party request

Time-zone lens

The same reset, in your clock.

Reset notices are stored in UTC. We default to your browser’s IANA time zone, account for daylight saving time, and keep UTC visible as the source of truth.

ShowingDetecting local time…
Choose another time zone
Use a region/city name, not a fixed EST or PST offset.