Bug with codex
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)?
latest
What subscription do you have?
pro
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
01a08c09-bcc8-7172-910a-f22a7d20dafa
Usage drained from 100% to 0% when i was getting nothing done, then kept hitting the model is at capacity " message and retrying to connect while using my hard-earned money to do nothing.
What steps can reproduce the bug?
Feedback ID: 01a08c09-bcc8-7172-910a-f22a7d20dafa
What is the expected behavior?
01a08c09-bcc8-7172-910a-f22a7d20dafa
Usage drained from 100% to 0% when i was getting nothing done, then kept hitting the model is at capacity " message and retrying to connect while using my hard-earned money to do nothing.
Additional information
01a08c09-bcc8-7172-910a-f22a7d20dafa
Usage drained from 100% to 0% when i was getting nothing done, then kept hitting the model is at capacity " message and retrying to connect while using my hard-earned money to do nothing.
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 reproducible steps; it provides feedback ID 01a08c09-bcc8-7172-910a-f22a7d20dafa and describes usage reaching 0% during model-capacity retries on Windows. Start by locating the usage accounting and retry entry points, then use the feedback record to determine whether failed capacity responses are being charged; done means the behavior is reproduced or its cause is identified and covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ai, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100