Bug: Weekly quota not reset in July 14 global reset (8M users milestone)

Open
#33,344 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Domain
backend

Research direction

Start by reproducing the issue with a business workspace account that has exhausted its weekly quota, then inspect the Usage UI after a global reset announcement. Compare the account state with accounts that received the reset and review issue #27027 for the earlier occurrence. Done means the announced reset applies to the affected account and the UI shows the updated quota and reset date.

Written by the indexing model from the issue text.

Description

app bug rate-limits

What issue are you seeing?

On July 14, 2026, Tibo announced a global usage limit reset for all Codex users to celebrate reaching 8 million active users:
https://x.com/thsottiaux/status/2077114635308986427

However, my account did not receive this reset. My weekly quota remains at 0% with a reset date of July 20 — unchanged from before the announcement. Other users in my network confirmed they received the
reset, so this appears to be an account-specific miss rather than a delayed rollout.

This is the same pattern as issue #27027 (June 4 global reset not applied to some accounts).

What steps can reproduce the bug?

  1. Have a business workspace account with exhausted weekly quota
  2. A global reset is announced by the Codex team
  3. Check the Usage UI — the reset date and quota percentage remain unchanged while other accounts receive the reset

Screenshot

See attached: after the July 14 reset announcement, the Usage UI still shows 0% remaining with a July 20 reset date.

Expected behavior

Global resets announced for "all" users should apply to all paid accounts, including business workspace accounts.

Additional information

  • Desktop app, latest version
  • This is a recurring issue — #27027 documents the same problem from the June 4 reset
  • The Usage UI provides no visibility into whether a special reset event was applied or skipped for a given account
Image
Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.