You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Credits were successfully added and visible (~2300 total), then later disappeared completely, dropping to 0 without any corresponding usage records after April 8, 2026. #19242
Windows 10 (Web UI)
Also accessing Codex via OpenCode
What terminal emulator and version are you using?
OpenCode (not official Codex CLI directly)
What issue are you seeing?
Summary
Credits were successfully added and visible (~2300 total), then later disappeared completely, dropping to 0 without any corresponding usage records after April 8, 2026.
Environment
Interface: Codex Web UI and OpenCode
Auth: ChatGPT Plus account
Model: GPT-5.4
Codex CLI version: 0.120.0
Account: same account/email used for payment
Payment source: official OpenAI billing (pay.openai.com)
Payment history
I have confirmed successful payments in this same account:
Invoice W4NJAXQX-0002 — March 31, 2026 — $40 for 1,000 credits
Invoice W4NJAXQX-0003 — April 18, 2026 — $40 for 1,000 credits
After the April 18 payment, I observed my total credits increase to approximately 2300+ credits.
Actual behavior
Credit balance now shows 0
Usage history only shows activity up to April 8, 2026
No usage entries appear after April 8
There is no visible record explaining how the credits were consumed
The issue is visible both in the Codex web UI and in OpenCode
The usage history appears frozen or desynchronized
Expected behavior
Credits purchased on March 31 and April 18 should remain unless consumed
If credits were consumed, usage history should show deductions after April 18
Credit balance and usage history should match
The dashboard should clearly show where credits were used
The system should not show 0 credits without corresponding usage logs
Why this seems like a bug
Credits were successfully purchased and temporarily visible
They later dropped to 0
There are no usage records after April 8 explaining the deduction
The absence of any usage records after the credits were added makes it impossible that the credits were consumed normally.
This suggests one of the following:
Backend credit ledger / synchronization issue
Missing or incomplete usage records
Incorrect credit accounting
Mismatch between billing system and Codex usage system
This behavior is observed across both Codex Web UI and OpenCode, suggesting it is not limited to a single interface.
Impact
Impossible to verify whether credits were used or lost
Loss of visibility into billing and usage
Reduced trust in credit accounting
Potential financial discrepancy (paid credits no longer visible)
Additional Evidence (Codex CLI /status)
Running /status shows:
Correct account (Plus subscription)
Usage limits present but flagged as "may be stale"
No credit balance information available
Example:
5h limit: 35% left
Weekly limit: 2% left
Warning: "limits may be stale"
This suggests system state (limits + credits) may be out of sync across services.
Screenshots
Screenshot 1: Codex usage dashboard (0 credits, no history after April 8)
Screenshot 2: April 18 payment receipt (1,000 credits)
Screenshot 3: March 31 payment receipt (1,000 credits)
Screenshot 4: /status output showing stale limits
Request
Please help determine whether this is:
a Codex backend credit accounting issue
a usage history tracking/display bug
a billing ledger synchronization issue
I can provide additional logs or details if needed.
changed the title [-]2000+ credits just went missing no usage history no what after buying the day before[/-][+]Credits were successfully added and visible (~2300 total), then later disappeared completely, dropping to 0 without any corresponding usage records after April 8, 2026.[/+]on Apr 24, 2026
Same symptom on a Free plan account today (2026-09-04). Adding it because I have 10-minute-interval telemetry across the transition, which I haven't seen posted in the other threads.
Setup: ChatGPT-account Codex over OAuth. A monitoring job polls GET /backend-api/codex/usage every ~10 min and records credits.balance and rate_limit.primary_window.used_percent.
Key context: the account's included 30-day window hit 100% on 2026-08-29 and stayed there. Codex kept working for the next six days, funded by the credit balance, which decreased steadily:
date
credits balance
08-28
1250.00
08-30
1205.92
09-01
1145.63
09-03
1033.18
09-04 08:17
1006.94
That is ~35 credits/day, so ~28 days of remaining runway.
The transition, two consecutive polls of the same endpoint:
The poller stayed healthy across the boundary: rate_limit rows kept being written from the same HTTP responses, only the credits block changed. In 916 samples over 7 days the balance had never been null before. Every Codex call fails since then with usage_limit_reached, resets_at = the 30-day window reset (Sep 26), not a credits-related reason.
and rate_limit_reset_credits is {"available_count": 0, "applicable_available_count": 0}.
Possibly the most useful detail: comparing the 429 response headers of this Free account against a Plus account on the same machine, same client, minutes apart:
header
Plus
this Free account
x-codex-plan-type
plus
absent
x-codex-primary-used-percent
100
absent
x-codex-primary-window-minutes
300
absent
x-codex-credits-has-credits
False
False
x-codex-credits-balance
0
empty string
The Plus account reports a numeric 0. This account reports an empty value, and three headers Plus receives are omitted entirely. An empty field reads like an absent credit record rather than a balance drawn down to zero, which lines up with @MajuriTK's read of this as a ledger/accounting problem rather than a UI or CLI inconsistency.
For tracing:x-oai-request-id: ac070f06-7d96-4ec8-9c38-4f39e6a3b7dc (2026-09-04T17:28:30Z). Account id and email available on request, I'd rather not post them here.
One difference worth flagging: the reports in this thread and in #19536, #18083 and #27598 are all paid plans. This one is a Free account that previously held a Plus subscription (lapsed 2026-02-07). If that matters for reproduction, happy to provide more.
Activity
github-actions commentedon Apr 24, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
[-]2000+ credits just went missing no usage history no what after buying the day before[/-][+]Credits were successfully added and visible (~2300 total), then later disappeared completely, dropping to 0 without any corresponding usage records after April 8, 2026.[/+]MajuriTK commentedon Apr 24, 2026
Additional clarification:
The key issue is not just inconsistent display.
Credits were visibly added (balance increased to ~2300), then later dropped to 0, with no usage records after April 8 explaining the deduction.
This suggests a potential credit ledger or accounting issue rather than a UI or CLI-only inconsistency.
etraut-openai commentedon Apr 24, 2026
@MajuriTK, I recommend that you contact OpenAI support.
zuuxuux commentedon Apr 25, 2026
I have just seen this too
MajuriTK commentedon Apr 25, 2026
@etraut-openai l did try sent them emails but 6 days now no responds l have been sending them but they dont respond am out of ideas
zuuxuux commentedon Apr 25, 2026
They have appalling customer support
midischwarz12 commentedon Apr 27, 2026
Yea, I just had a similar issue as well.
mherrerap87 commentedon Sep 4, 2026
Same symptom on a Free plan account today (2026-09-04). Adding it because I have 10-minute-interval telemetry across the transition, which I haven't seen posted in the other threads.
Setup: ChatGPT-account Codex over OAuth. A monitoring job polls
GET /backend-api/codex/usageevery ~10 min and recordscredits.balanceandrate_limit.primary_window.used_percent.Key context: the account's included 30-day window hit 100% on 2026-08-29 and stayed there. Codex kept working for the next six days, funded by the credit balance, which decreased steadily:
That is ~35 credits/day, so ~28 days of remaining runway.
The transition, two consecutive polls of the same endpoint:
The poller stayed healthy across the boundary:
rate_limitrows kept being written from the same HTTP responses, only thecreditsblock changed. In 916 samples over 7 days the balance had never been null before. Every Codex call fails since then withusage_limit_reached,resets_at= the 30-day window reset (Sep 26), not a credits-related reason.creditsnow reads:{"has_credits": false, "unlimited": false, "overage_limit_reached": false, "balance": null, "approx_local_messages": null, "approx_cloud_messages": null}and
rate_limit_reset_creditsis{"available_count": 0, "applicable_available_count": 0}.Possibly the most useful detail: comparing the 429 response headers of this Free account against a Plus account on the same machine, same client, minutes apart:
x-codex-plan-typeplusx-codex-primary-used-percent100x-codex-primary-window-minutes300x-codex-credits-has-creditsFalseFalsex-codex-credits-balance0The Plus account reports a numeric
0. This account reports an empty value, and three headers Plus receives are omitted entirely. An empty field reads like an absent credit record rather than a balance drawn down to zero, which lines up with @MajuriTK's read of this as a ledger/accounting problem rather than a UI or CLI inconsistency.For tracing:
x-oai-request-id: ac070f06-7d96-4ec8-9c38-4f39e6a3b7dc(2026-09-04T17:28:30Z). Account id and email available on request, I'd rather not post them here.One difference worth flagging: the reports in this thread and in #19536, #18083 and #27598 are all paid plans. This one is a Free account that previously held a Plus subscription (lapsed 2026-02-07). If that matters for reproduction, happy to provide more.