Subscription Status
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of Codex CLI is running?
cli 0.153.4
What subscription do you have?
Pro
Which model were you using?
Astra default
What platform is your computer?
Win 11
What terminal emulator and version are you using (if applicable)?
VS Code
Codex doctor report
What issue are you seeing?
My account in /status show Pro Lite, and says I burned up my weekly limit-nearly impossible. I have a Pro account. Why does codex think I have a pro lite and it shut down? Please look into my billing and restore my codex service.
What steps can reproduce the bug?
Uploaded thread: 01a0a570-fc31-7523-8eb8-18e5eb960054
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 with the Codex CLI /status output and the uploaded thread 01a0a570-fc31-7523-8eb8-18e5eb960054; no source file or test is identified. Reproduce on Windows 11 with Codex CLI 0.153.4 and verify how the Pro account is classified. Done means the displayed plan and weekly-limit state match the account and the service is not incorrectly shut down.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100