I did not receive the banked Codex reset from Tibo’s “sneaky double reset” announcement.
Open 💬 2 comments Opened Jun 18, 2026 by xianull
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
26.611.62324
What subscription do you have?
pro 5x
What platform is your computer?
_No response_
What issue are you seeing?
I did not receive the banked Codex reset from Tibo’s “sneaky double reset” announcement. The post said users would get both a full reset and one reset added to the reset bank, but my Codex profile/usage summary shows no “1 reset available.”
Plan: pro
Codex App version: 26.611.62324
Platform: macOS
Expected: one banked reset available
Actual: no banked reset shown
What steps can reproduce the bug?
I did not receive the banked Codex reset from Tibo’s “sneaky double reset” announcement. The post said users would get both a full reset and one reset added to the reset bank, but my Codex profile/usage summary shows no “1 reset available.”
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Same situation here.
I understood that we were meant to receive one banked Codex reset around the launch of this feature, and I didn’t receive that either. I’ve also seen some other users on X reporting similar issues with banked resets not appearing as expected.
My quota did get forcefully reset, but I’ve still never seen any banked resets in the Codex app usage UI.
Plan: Pro 20x
OS: Windows
Codex App version: 26.611.62324
This looks more like a backend/account entitlement issue than a client UI issue.
I inspected the app traffic externally, and the reset-credit state still appears to be zero.
Sanitised usage/reset-credit state:
{
"plan_type": "pro",
"rate_limit_allowed": true,
"rate_limit_limit_reached": false,
"rate_limit_reached_type": null,
"rate_limit_reset_credits": {
"available_count": 0
}
}
Reset-credit list response:
{
"available_count": 0,
"credits": []
}
Hopefully this helps narrow it down.