Pro account missing Codex reset bank and invite/referral entitlement
What version of the Codex App are you using (From “About Codex” dialog)?
26.609.71450 MSIX package: 26.609.9530.0
What subscription do you have?
ChatGPT Pro, $200/month. I have been continuously subscribed for several months.
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
<img width="586" height="596" alt="Image" src="https://github.com/user-attachments/assets/db829951-4c6a-4a15-86ba-ffc57c1bb9a9" />
My Pro account does not show the Codex rate-limit reset bank, reset count, Reset usage option, or Invite a friend/referral option.
I inspected the installed Windows App bundle and confirmed the feature code exists in app.asar. The app has UI strings for "Invite a friend", "Invite a coworker", "Reset usage", and reset-credit states.
The relevant code appears to hide these features unless the server returns entitlement/eligibility, e.g.:
- referral requires eligibility?.should_show === true
- reset bank depends on rate_limit_reset_credits?.available_count
So this looks like a server-side entitlement/eligibility bug for my Pro account, not a missing app feature.
What steps can reproduce the bug?
- Sign in to Windows Codex App with my ChatGPT Pro account.
- Open the left-bottom account / usage menu.
- Check Usage remaining and the profile/account menu.
- No reset bank, Reset usage, or Invite a friend/referral option appears.
What is the expected behavior?
As a Pro subscriber, I should receive at least the same Codex promotional entitlement as Plus users, including reset credit(s) and invite/referral access.
Please correct my account entitlement and provide fair compensation for the missing reset/referral benefit.
Additional information
Installed bundle evidence:
- app.asar contains referral and reset-bank code.
- Invite UI: profile-dropdown-JfhyK1aB.js
- Reset UI: rate-limit-reset-modal-BlVuSxxm.js
- API hooks: codex-api-D75Uc14P.js
- Endpoints present: /referrals/invite/eligibility, /wham/rate-limit-reset-credits, /wham/rate-limit-reset-credits/consume
This strongly suggests my account is not receiving the correct server-side eligibility or rate_limit_reset_credits.available_count state.
7 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Hey, I'm running into the same issue. It hasn't been resolved yet, and actually, a lot of people are experiencing this. OpenAI really ought to pay attention to this.
I reviewed #28110, #28251, and #28028.
This is related to the same reset/referral subsystem, but it is not an exact duplicate of #28251 or #28028. Those issues describe users who previously had invite/reset eligibility and then lost it, or whose invite flow consumed quota / failed to grant rewards.
My case is different: my Pro account does not receive the reset bank or invite/referral entitlement in the first place. The installed Windows App contains the relevant UI/API code, but the runtime eligibility request for
codex_referral_persistent_invitereturns 403, so this appears to be an account/server-side eligibility problem rather than an invite-flow state/retry issue.#28110 may be the closest related report, but my report adds Pro-account impact and concrete app/API evidence.
I also do not have any resets, and I have had my account longer than the Jun 12 introduction. I should have 3 AFAIK
I received reset an hour after posting above
there is something weird for sure, maybe tiered release or a cutoff or backoff based on subscription dates?
I also got none, went to check on the Codex CLI now that 0.142.0 got released and I could reset, but have nothing banked.
I’m seeing a related issue on macOS.
Codex search surfaces the invite setting, but selecting it only opens Profile and no invite option appears.
A local Codex log shows the eligibility request was attempted:
GET /referrals/invite/eligibility?referral_key=codex_referral_persistent_invite&supports_rewardless_invites=true
At that time it failed with net::ERR_ADDRESS_UNREACHABLE (the app recorded status 500)