ConfirmedcodexAll Codex plans.

Codex usage limits reset across all plans for plugins

Tibo confirmed a Codex usage-limit reset across all plans so users could experiment with newly launched plugins.

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

The stated purpose was to let users experiment with newly launched Codex plugins, with Tibo also noting that it had been a while since the previous reset.

Who was affected

This is one of the clearest scope statements in the ledger because the first-party post explicitly says the reset covered all Codex plans.

How precise is the timing?

The X Post time is used as the conservative announcement anchor. The source says the reset had occurred, but gives no separate propagation-completion timestamp.

Why this record matters

The trigger was product adoption rather than an outage: a broad reset was used to encourage exploration of a newly released capability across every plan.

Evidence

Attached sources

  1. Tibo SottiauxX · x postRetrieval: available

    We have reset Codex usage limits across all plans to let everyone experiment with the magnificent plugins we just launched.

    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.