Astra XHigh from 60%+ to 12% to remaining tokens in less than 5 minutes.

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

0.153.4

What subscription do you have?

Pro 200

What platform is your computer?

Linux

What issue are you seeing?

main now contains all three committed fixes. The remaining 11 modified and 4 untracked files.
I preserved these changes. They are uncommitted and unvalidated, and were excluded from the rebuilt executable.

A few seconds before I had run /status twice on a difference instance and got 60%.

› can you validate them?

• I’ll validate the uncommitted code and prompt changes, then review the project-network proposal for consistency. I’ll leave the changes uncommitted.

• Explored ....

Read a few files, write a few tail statements.

Noticed this:
⚠ Heads up, you have less than 25% of your weekly limit left. Run /status for a breakdown.

Checked and got:

What steps can reproduce the bug?

Feedback ticket: 01a08611-2b24-7741-b139-fb9e2e39c56a

What is the expected behavior?

Not consume 50% of the 200 USD account in a few turns of doing nothing.

Additional information

Feedback ticket: 01a08611-2b24-7741-b139-fb9e2e39c56a

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

Powered by Codex Action

Same thing happened to me, went from 44% to 2% in 5 minutes

same for me went from 80% to 1% on Astra xhigh

Mine went from 68% to 83%

Same here jumped from 61% to 8% in a few seconds

same here from 50% to 0%

~85% to 0% instantly

this happened to me as well. went from 30% to 0% instantly.

SAME THIGN happend from 93 to 9

same issue here, what on earth... all my AI agents' work got interrupted too!

Everyone check your reset date. Mine now says 9/11. That was the weekly reset date before we got the Monday reset. I think what happened was the Monday reset got undone somehow.

same issue. dropped to 1%

Finally, I can sit back, relax, watch my usage hit 0%, and enjoy the comforting thought that Tibo owes me a banked reset.

@dleake14

Adding local telemetry from a macOS Pro account that hit this in the same window. The rollout logs and the /status pane below come from the same session, 01a08701-e341-7cd0-8b7a-329af7a590f7.

Environment: codex-cli 0.153.4, macOS 26.5.2 (arm64), Pro plan, model = "gpt-6-astra", model_reasoning_effort = "xhigh", machine timezone UTC-4.

The server changed the account's rate-limit bucket mid-second

~/.codex/sessions records every rate_limits payload the server returns. Two consecutive payloads, 774 ms apart:

2026-09-09T17:14:26.078Z  {"limit_id":"codex","plan_type":"pro","primary":{"used_percent":36.0,"window_minutes":10080,"resets_at":1789436774},"secondary":null}
2026-09-09T17:14:26.852Z  {"limit_id":"premium","plan_type":"pro","primary":null,"secondary":null}

limit_id went from codex to premium, and primary went to null. No window, no percentage, no reset timestamp.

What `/status` showed afterwards

>_ OpenAI Codex (v0.153.4)

 Model:              gpt-6-astra (reasoning xhigh, summa
 Directory:          ~/.claude/skills
 Account:            <redacted> (Pro)
 Session:            01a08701-e341-7cd0-8b7a-329af7a590f

 Context window:     30% left (183K used / 258K)
 Weekly limit:       [░░░░░░░░░░░░░░░░░░░░] 0% left
                     (resets 14:10 on 12 Sep)
 GPT-5.3-Codex-Spark limit:
 5h limit:           [████████████████████] 100% left
                     (resets 18:25)
 Weekly limit:       [████████████████████] 100% left
                     (resets 13:25 on 16 Sep)
 premium limit:

Three things to note in that pane:

The weekly limit reads 0% left. The last logged reading before the switch was 36% used, so 64% left. Nothing ran in between.
The weekly reset moved backwards. The logged resets_at was 1789436774 = 2026-09-15T01:46:14Z. /status now shows 14:10 on 12 Sep local = 2026-09-12T18:10Z, roughly 2.8 days earlier. This matches what @dleake14 reported about reset dates.
The premium limit: section renders with nothing under it, which is what "primary": null gives the client. A new GPT-5.3-Codex-Spark limit: section appeared alongside it with both windows at 100% left.

Usage history on this account before the switch

No jump, no anomaly, a steady climb over two days:

2026-09-08T18:32:31Z  codex  18%  window_minutes=10080  resets_at=2026-09-15T01:46:14Z
2026-09-08T23:40:50Z  codex  23%
2026-09-09T04:38:59Z  codex  26%
2026-09-09T12:30:35Z  codex  27%
2026-09-09T15:53:41Z  codex  33%
2026-09-09T16:48:01Z  codex  36%
2026-09-09T17:14:26Z  codex  36%   <- last reading before the switch

Three bucket ids in rotation

Across every rollout on this machine since 2026-09-01:

`limit_id`	snapshots	first seen	last seen	ever non-null `primary`
`codex`	34427	2026-09-01T04:20:32Z	2026-09-09T17:14:26Z	yes
`codex_bengalfox`	735	2026-09-03T16:06:37Z	2026-09-09T13:58:30Z	yes
`premium`	39	2026-09-07T04:23:35Z	2026-09-09T17:20:01Z	no, 0 of 39

premium has never once carried usage data on this account.

Check your own rollouts

python3 - <<'EOF' | sort
import json,glob,os
def f(d):
    if isinstance(d,dict):
        if isinstance(d.get('rate_limits'),dict): return d['rate_limits']
        for v in d.values():
            r=f(v)
            if r: return r
    elif isinstance(d,list):
        for v in d:
            r=f(v)
            if r: return r
for p in glob.glob(os.path.expanduser('~/.codex/sessions/*/*/*/*.jsonl')):
    for l in open(p,errors='ignore'):
        if '"rate_limits"' not in l: continue
        try: o=json.loads(l)
        except: continue
        r=f(o)
        if r: print(o.get('timestamp'), r.get('limit_id'), (r.get('primary') or {}).get('used_percent'))
EOF

The reports in this thread show percentages moving in both directions, including one going up. A quota bucket being swapped for another one, with different accounting and a different reset boundary, would produce that mix. Worth checking whether the bucket reassignment around 17:14Z on 2026-09-09 was intended, and whether usage accrued under codex was carried over or re-derived under the new bucket and its earlier reset date.

I was at 16% used, and now it's showing 86% used. Something is wrong.

Same here, went from 60% left to 0 in a second.

Same here, from 78% to 0% in a single prompt!

Haha if you look at the active ticket tree right now.. This happened globally lol. For kicks it happened to me too. This looks like the OG ticket so I'll comment here.

Similar situation, but not exactly. I was on Astra Low and switched to daybreak-blue-latest low: #44232

On one acc i was at 20% now im at 70%
And the other one, i was at 0 now im at 5%
I think i stole your tokens

my usage limit got back, but it messed up ongoing work, thanks so much for screwing over everyone, @openai 👎

Haha they changed that back quickly now didn't they. Just reset for me peeps. I vote free resets all around!

Oh man, over on Reddit and Twitter people pulled the trigger on their banked resets.. ooph!

same for me, went from 100% to 64% in ~ 6m 5s, here's the full report:
https://x.com/AryanTiwariHQ/status/2097746044511822216?s=20

Separate same-day case on ChatGPT Pro 20x / $200-monthly, macOS Apple Silicon:

My weekly allowance was around 3% remaining. At 12:35:53 PM CDT on September 9, the official Usage page showed 30% remaining. At 12:42:35 PM CDT, it showed 3% remaining again.

~3% remaining → 30% remaining → 3% remaining

I had Codex work running while the 30% state was visible. After the Usage page returned to the earlier state, I used a Full reset, but the weekly allowance still did not restore and remained around 3%. I’m not sure whether the reset request was accepted.

I attached timestamped official Usage screenshots showing the two states. My earlier, separate quota report is #42912:
#42912

Timestamped evidence from a separate Pro 20x / macOS case (reset-credit controls cropped out):

Before this sequence, the weekly allowance was around 3% remaining.
12:35:53 PM CDT: the official Usage page showed 30% remaining.
12:42:35 PM CDT: it showed 3% remaining again.

After the display returned to 3%, I used a Full reset, but the weekly allowance did not restore. I’m not sure what happened.

My usage limit went back yesterday, to where it was before the sudden drop, however, when it went back up, it also changed my weekly period - it changed when the next Weekly reset happens.
I had Weekly usage limit Resets Sep 14, 2026, 5:37 AM before the limit fix, and immediately after I had Weekly usage limit Resets Sep 16, 2026, 3:16 PM. The time when I used the banked reset.
This must have been part of the problem (bug) and it points towards a nasty change. The banked resets should not move the Weeekly window otherwise what is the point? If I have the Weekly reset tomorrow, and I use a banked reset today, it basically means I forfait almost an entire week of usage in your favor. This does not seem fair and makes no sense to me.

Navigation Menu

Repository navigation

Astra XHigh from 60%+ to 12% to remaining tokens in less than 5 minutes. #44205

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

What subscription do you have?

What platform is your computer?

What issue are you seeing?

What steps can reproduce the bug?

What is the expected behavior?

Additional information

3 remaining items

The server changed the account's rate-limit bucket mid-second

What `/status` showed afterwards

Usage history on this account before the switch

Three bucket ids in rotation

Check your own rollouts

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Astra XHigh from 60%+ to 12% to remaining tokens in less than 5 minutes. #44205

Description

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

What subscription do you have?

What platform is your computer?

What issue are you seeing?

What steps can reproduce the bug?

What is the expected behavior?

Additional information

Activity

github-actions commented on Sep 9, 2026

FernandoIGD commented on Sep 9, 2026

tarunyadav1 commented on Sep 9, 2026

infcodev commented on Sep 9, 2026

iantocristian commented on Sep 9, 2026

romainsimon commented on Sep 9, 2026

Kylyi commented on Sep 9, 2026

asenju commented on Sep 9, 2026

kanok22 commented on Sep 9, 2026

otanim commented on Sep 9, 2026

dleake14 commented on Sep 9, 2026

shubham-wf commented on Sep 9, 2026

3 remaining items

tonybolivar commented on Sep 9, 2026

WTF-Am-ID commented on Sep 9, 2026

The server changed the account's rate-limit bucket mid-second

What /status showed afterwards

Usage history on this account before the switch

Three bucket ids in rotation

Check your own rollouts

diorrego commented on Sep 9, 2026

danielterwiel commented on Sep 9, 2026

dtsoltero commented on Sep 9, 2026

hdusten commented on Sep 9, 2026

Oichkatzelesfrettschen commented on Sep 9, 2026

Antoninnnnnnnn commented on Sep 9, 2026

otanim commented on Sep 9, 2026

hdusten commented on Sep 9, 2026

hdusten commented on Sep 9, 2026

sudoSwami commented on Sep 9, 2026

Nebulazer123 commented on Sep 9, 2026

Nebulazer123 commented on Sep 9, 2026

iantocristian commented on Sep 10, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

What `/status` showed afterwards