Banked Full Reset cannot be redeemed: “Couldn't reset usage. Please try again”

Open 💬 1 comment Opened Jul 20, 2026 by Hamster-Baron

What version of the Codex App are you using (From “About Codex” dialog)?

26.715.31925

What subscription do you have?

Pro 5x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

I have one available banked Codex Full Reset, but I am unable to redeem it.

Whenever I click “Use reset”, the following error appears:

“Couldn't reset usage. Please try again.”

The issue occurs consistently across multiple devices and clients, including the Codex web interface and the Codex CLI/TUI.

Current state:

  • Available banked resets: 1
  • Reset type: Full reset
  • Banked reset expiration date: August 13, 2026

After the failed attempt:

  • Weekly usage remains unchanged
  • The available reset count remains at 1
  • The Full Reset is still displayed as available

Because the same failure occurs on different devices and through both the web interface and Codex CLI/TUI, this appears to be an account-side or server-side reset redemption issue rather than a local problem.

What steps can reproduce the bug?

  1. Sign in to an account that has an available banked Codex Full Reset.
  2. Open the Codex usage page, or open the /usage menu in Codex CLI/TUI.
  3. Confirm that one Full Reset is shown as available.
  4. Click or select “Use reset”.
  5. Confirm the reset operation when prompted.
  6. Observe the error message:

“Couldn't reset usage. Please try again.”

  1. Check the usage page again.
  2. Observe that the weekly usage has not been reset and the available reset count is still 1.

The issue can be reproduced on:

  • Codex web interface
  • Codex CLI/TUI
  • Multiple devices

<img width="526" height="431" alt="Image" src="https://github.com/user-attachments/assets/bdcf55f9-448c-479e-bdcc-d5ff64d7dcd4" />

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗