/status causes a limits reset
Open
Nobody has claimed this yet.
bug
CLI
rate-limits
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
codex-cli 0.153.4
What subscription do you have?
Pro
Which model were you using?
No response
What platform is your computer?
No response
What terminal emulator and version are you using (if applicable)?
iTerm2
Codex doctor report
What issue are you seeing?
/status caused an unintentional /reset
What steps can reproduce the bug?
Uploaded thread: 01a08159-6b32-7c41-8706-8efd05f70c13
What is the expected behavior?
No response
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 reported behavior with codex-cli 0.153.4, using the uploaded thread 01a08159-6b32-7c41-8706-8efd05f70c13 as the reproduction context. Trace the /status and /reset entry points and determine why invoking /status resets limits; done means /status reports status without triggering an unintended reset.
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
- Needs clarification
- Newbie friendliness
- 45/100