Being rate limited after applying on demand reset.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.818.61809
What subscription do you have?
Pro 20X
What platform is your computer?
Darwin 25.6.0 arm64 arm Mac OS
What issue are you seeing?
I had a goal running with Ultra Sol, ran out of usage (hit 0%).
Applied the on demand reset I had banked, usage went back to 100%.
Session ID: 01a03a52-00bd-7c83-9ebe-064f78e2ce65
Tried to resume the goal, but immediately hit with the 429 error. I tried logging out, and then back in, same issue, I've tried restarting the app, same issue, I tried waiting a few hours, same issue. Tried starting a whole new prompt, immediately 429'd
What steps can reproduce the bug?
Hit 0%, apply a reset, and try to resume.
What is the expected behavior?
Not to be rate limited
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source file, test, or entry point. Start by tracing the 429 response and the on-demand reset flow in the Codex app, then reproduce the zero-usage reset scenario. Done means a reset permits new and resumed prompts without an immediate rate-limit error, with coverage for the reported sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100