ConfirmedsharedChatGPT Work and Codex users; plan exclusions were not stated.

ChatGPT Work and Codex received a full usage reset

Tibo announced a full usage reset for ChatGPT Work and Codex and said propagation would continue during the following hour.

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 verified announcement offered a full reset while welcoming a new model-research contributor; it did not attribute the reset to an outage or incorrect usage accounting.

Who was affected

The named product scope was ChatGPT Work and Codex. The post did not specify subscription tiers, so the record does not expand the claim to every paid account.

How precise is the timing?

Tibo said propagation would continue during the following hour. The stored Post time is therefore the start-of-announcement anchor, not the end of rollout for every user.

Why this record matters

This is an early shared-pool record naming both ChatGPT Work and Codex, and it demonstrates why announcement time and expected propagation window must remain distinct.

Evidence

Attached sources

  1. Tibo SottiauxX · x postRetrieval: available

    Enjoy a full reset of your usage limits for ChatGPT Work and Codex. Propagating in the next hour.

    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.