ConfirmedcodexEveryone using GPT-5-Codex; plan-level exclusions were not stated.

GPT-5-Codex limits reset after capacity slowdowns

Tibo confirmed a reset of everyone’s GPT-5-Codex limits after slowdowns while OpenAI added GPU capacity.

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 tied the reset to earlier GPT-5-Codex slowdowns while OpenAI was provisioning additional GPU capacity, framing the reset as compensation and a way to restore useful access.

Who was affected

The post said everyone’s GPT-5-Codex limits were reset, but it did not enumerate subscription tiers or any account-level exclusions.

How precise is the timing?

The stored time is the X announcement timestamp. The post confirms the reset had been performed by then, but it does not publish a separate all-account propagation completion time.

Why this record matters

This is the earliest sourced reset in the current ledger and establishes a recurring pattern: capacity or reliability disruption can lead to a broad goodwill reset.

Evidence

Attached sources

  1. Tibo SottiauxX · x postRetrieval: available

    We have reset everyone's limits for gpt-5-codex to allow you all to benefit more from it today and as a way to make up for the slowdowns earlier.

    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.