OpenAI announces a worldwide usage reset after DevDay 2026

What happened

OpenAI announced a worldwide usage reset at the end of its DevDay 2026 keynote on 29 September. In automatic captions from the official OpenAI keynote, the speaker says OpenAI figured developers “might need another banked reset,” asks for “a low-key reset for everybody here,” and then says after the countdown: “that’s obviously for everyone in the world, not just people here at DevDay.”

The captions identify a person named Tibo, but do not provide a surname or title. OpenAI’s event profile names him Thibault “Tibo” Sottiaux, who leads Codex. The keynote itself is the primary evidence for the announcement.

The original post, by a community moderator, on OpenAI’s DevDay developer-community thread also says that a worldwide usage reset was announced at the end. That community post echoes the keynote moment, but it is not a separate OpenAI product statement.

What is confirmed, and what is not

The keynote confirms that OpenAI announced a reset “for everyone in the world.” It does not specify:

• which limits were reset;
• whether the reset covers Codex, ChatGPT Work, the API, or other products;
• whether free and Plus users are included;
• whether the reset has already reached every account;
• how banked resets are treated in this event;
• whether the reset is a one-time event or part of a recurring policy.

OpenAI’s help-centre page defines a “banked reset” as a saved, one-time Codex usage-limit reset, but it does not say which products or plans this event covers, and no written OpenAI statement about the reset was identified. Users should check their own usage page rather than assume that the announcement has already changed their account.

Why it matters to developers

Usage resets affect more than a counter on a dashboard. Developers plan work around usage windows and the availability of banked resets.

A reset can create room for a large coding session, but the treatment of banked resets in this event is not documented.

Developers should check:

1. the current usage page for each relevant OpenAI product;
2. whether the available allowance changed;
3. whether banked resets remain available;
4. which product or model the allowance applies to;
5. when the next usage window begins;
6. whether team or workspace limits differ from personal limits.

Bottom line

OpenAI announced a worldwide usage reset at the end of its 29 September DevDay keynote. That announcement is confirmed by the keynote’s automatic captions and echoed by the community post.

The operational details are still missing. Until OpenAI documents which products and limits are covered, developers should treat the reset as an announcement rather than a guaranteed account-level change. Check the usage page, verify the allowance directly, and do not plan critical work around quota that has not appeared.