I spent my usage waiting for Tibo’s 7M reset, but the reset never came

Open 💬 5 comments Opened Jul 14, 2026 by AiurArtanis

What issue are you seeing?

Summary

St. Tibo announced that all Work and Codex users would receive one banked reset to celebrate reaching 7 million active users last day.

Unfortunately, mine seems to have gotten lost somewhere between the celebration confetti and my Usage page.

What happened

When the 5-hour usage limit was temporarily removed, I took that as a clear invitation to put my agents to work.

So I did.

I worked them relentlessly, burned through my weekly usage, and kept telling myself:

“It’s fine. Tibo’s 7M milestone reset will arrive soon and keep this operation alive.”

The milestone arrived.

The reset did not.

My agents are exhausted, my remaining usage is on life support, and the promised emergency ration pack is nowhere to be found.

I have checked:

  • The Usage page on ChatGPT web
  • The ChatGPT desktop app
  • Codex settings and usage dashboard
  • After signing out and signing back in
  • After updating the desktop app

There is still no banked reset available.

Expected behavior

One banked reset should appear on my account and be available to redeem, as announced for the 7M active-user milestone.

Actual behavior

No banked reset is shown on either the web or desktop app.

Environment

  • ChatGPT plan: [Plus / Pro / Business]
  • Platform: Windows
  • ChatGPT desktop app version: [version]
  • Codex CLI version, if applicable: [version]
  • Region: [region]
  • Approximate time checked: [date and timezone]

Could you please confirm whether the rollout is still in progress, or whether my account may have been missed?

I am not asking for special treatment. I am merely requesting the promised healing potion before my agent factory collapses.

What steps can reproduce the bug?

open ~Codex~ ChatGPT app and check out usage

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗