Codex agent used a reset token while I had 100% usage remaining
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.901.51231
What subscription do you have?
20x Pro
What platform is your computer?
MacOS
What issue are you seeing?
I used a banked reset, which reset my usage to 100%.
I had a session that stopped working due to running out of usage, which makes sense.
I then told it that I reset my usage and to resume the work. The agent misunderstood and it then instead did its own usage reset claim without any warning or confirmation.
Under no circumstance should this happen, where it uses a usage token while I'm literally at 100% usage remaining. I understand in some workflows users might want this to happen without confirmation, but it should have a confirmation especially while >20% usage remaining. "Are you sure you want to redeem a token reset? You have 100% of your usage remaining currently" would have saved me here.
What steps can reproduce the bug?
Feedback ID: 01a08194-6036-7d93-9c80-31aeafe8c699
What is the expected behavior?
The app should issue a confirmation to use a token reset, at least while a certain threshold is remaining still. The model can misinterpret intent of the user on using a token reset, which is okay, but the app itself should safeguard this with a confirmation.
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
Start by reproducing the reset flow using feedback ID 01a08194-6036-7d93-9c80-31aeafe8c699, then trace where the agent redeems a usage reset after the user says to resume work. Done means the app requests confirmation before redeeming a token when substantial usage remains, including the reported 100% case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100