[Bug] Free reset changed weekly reset_at without restoring allowance

Open
#34,874 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
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
rust
Domain
backend

Research direction

No repository file, test, or entry point is identified. Start by reviewing the reset handling associated with feedback ID no-active-thread-019f8d3c-1f1c-7f12-9f92-e62e00bd213e and the private support case 11775963. Done means confirming whether reset_at and allowance restoration can diverge, then documenting or testing consistent behavior.

Written by the indexing model from the issue text.

Description

app bug rate-limits windows-os
Environment
  • Codex for Windows 26.715.12143
  • ChatGPT Plus
  • Windows 11
  • Not model-specific
Issue

A free Codex usage reset may have advanced the backend weekly reset_at timestamp without applying the corresponding weekly allowance replenishment.

Observed sequence:

  • Jul 18, 2026: next reset showed Jul 24.
  • Jul 19: it changed to Jul 25.
  • Jul 20: it changed to Jul 26.
  • During this period, the weekly allowance did not replenish.
  • Codex remained usable and usage continued to be deducted.
  • Refreshing, signing out/in, changing browsers, devices, networks, and VPN settings did not correct the day-level change.
  • A later free reset restored the allowance to 100%.
  • Two remaining manual Full reset credits were unchanged, so I did not trigger that restoration manually.
  • After normal usage, the page showed a new reset time of Jul 29, 2026 at 10:26.
Suspected behavior

An earlier free reset may have updated the weekly window and reset_at, but failed to apply the allowance restoration. A later free reset appears to have applied both.

This is a hypothesis requiring backend verification.

Expected behavior

A free reset should update the reset window and replenish the allowance consistently, or leave both unchanged.

Diagnostics

Feedback ID: no-active-thread-019f8d3c-1f1c-7f12-9f92-e62e00bd213e

Private Support case with sanitized HAR and account evidence: 11775963

I will not upload the HAR publicly.

Please check whether free/special reset events can update reset_at independently from allowance restoration, causing a partial failure.

Related to #9508, but this report concerns a possible partial reset failure.

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.