ConfirmedsharedAll ChatGPT Work and Codex users.

All ChatGPT Work and Codex usage limits reset

Tibo confirmed he had reset usage limits for all ChatGPT Work and Codex users while sharing an update on GPT-5.6 Sol limits.

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 confirmed the reset while giving an update on reports that GPT-5.6 Sol appeared to consume Codex limits faster than users expected; the record does not overstate that context as a proven single defect.

Who was affected

The announcement explicitly said all ChatGPT Work and Codex users, so the product and user scope is broader than records limited to named plans or cohorts.

How precise is the timing?

The X timestamp is the first-party announcement anchor. The source confirms the action was taken but does not publish a separate backend completion time for every account.

Why this record matters

This record links a broad reset with a usage-efficiency clarification around GPT-5.6 Sol, making it independently useful beyond a line in the chronological feed.

Evidence

Attached sources

  1. Tibo SottiauxX · x postRetrieval: available

    I've reset usage limits for all ChatGPT Work and Codex users.

    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.