Clarify Codex rate-limit reset behavior and make reset scope visible in Usage UI

What variant of Codex are you using?

Codex for macOS

What version of the Codex App are you using?

Version 26.422.71525 (2210)

What subscription do you have?

Plus

What platform is your computer?

macOS Tahoe

What issue are you seeing?

A public announcement stated that Codex rate limits were reset for “ALL paid plans.” The announcement was posted by Tibo Sottiaux (@thsottiaux) on X on April 28, 2026:

Don’t just reset Codex rate limits for fun, it costs money. Don’t just reset Codex rate limits for fun, it costs money. ... but the vibes are good ... I have reset Codex rate limits for ALL paid plans to celebrate a good week and allow everyone to build more with GPT-5.5. Enjoy

Reference: https://x.com/thsottiaux/status/2048997818673537399?s=46&t=T-QN-YBrEo1iiw5oRoIM_Q

However, the Codex Usage UI did not make clear what was actually reset, which quota intervals were included, or whether the reset applied uniformly across paid plans.

In my case, after the announcement, my account continued to show depleted / partially depleted Codex usage, including the weekly limit remaining on its normal cycle. OpenAI Support later clarified that the reset did not universally apply across all quota types or account states, and that the weekly Codex limit was not reset for all users, including my Plus account.

That means the product currently has a transparency gap:

• The public wording suggested a broad paid-plan rate-limit reset.
• The actual implementation appears to have been conditional by quota interval, account state, usage timing, or backend eligibility.
• The Usage UI did not show whether a special reset had been applied.
• The Usage UI did not explain which limits were eligible or excluded.
• Users could not distinguish between an ordinary scheduled timer refresh and a special announced reset.

What steps can reproduce the issue?

1. Use Codex on a paid Plus account with active usage already consumed.
2. View Codex Usage after a public rate-limit reset announcement.
3. Compare the visible 5-hour and weekly usage limits.
4. Observe that the UI does not indicate:

• whether a special reset was applied;
• which quota interval was reset;
• whether the weekly limit was excluded;
• whether reset eligibility depended on account state or timing.

What is the expected behavior?

When a special rate-limit reset is applied, Codex should clearly show what changed.

For example, the Usage UI could display:

• “Special reset applied”
• timestamp of reset application;
• affected quota interval(s), such as 5-hour only, weekly only, or both;
• whether any quota interval was excluded;
• if reset behavior depends on backend eligibility, a short explanation.

Public reset announcements should also match the visible product behavior. If only selected quota windows are reset, wording should specify “5-hour window,” “shorter interval limits,” or “eligible quota states,” rather than broadly saying “Codex rate limits for ALL paid plans.”

Actual behavior

The Usage UI continued to show ordinary usage-cycle values and did not indicate whether any special reset had applied.

Support later explained that:

• the reset was not a blanket override across all quota types;
• the weekly limit was not universally reset;
• reset behavior depended on quota interval, usage timing, account state, and technical eligibility;
• no correction would be made where the weekly limit continued on its normal cycle.

That may be intended backend behavior, but the current UI and public wording do not make that operational scope clear to users.

Why this matters

Codex exposes multiple visible usage limits, including shorter rolling windows and weekly limits. When OpenAI announces a reset of “Codex rate limits for ALL paid plans,” paid users reasonably expect the product to make clear which visible limits were actually reset.

Without that transparency, users cannot tell whether:

• the reset failed to propagate;
• only the 5-hour window was reset;
• the weekly limit was intentionally excluded;
• their account was ineligible due to backend state;
• or the UI simply does not reflect the reset.

Requested improvement

Please clarify and improve Codex usage visibility around special resets:

1. Show whether a special reset was applied to the account.
2. Show which quota intervals were affected.
3. Show whether the weekly limit was included or excluded.
4. Make reset announcements align with the actual quota behavior.
5. Consider adding reset-event history to the Usage page or /status.

Additional information

This is not a request for credits. It is a request for clearer Codex quota transparency and reset-scope visibility.