Incantation for calculating Codex usage and one other issue no-active-thread-01a0971a-1833-7dc2-8eb9-8f8b118ff59d
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.908.40401 There is no About Codex dialog, and the About ChatGPT doesn't allow cut/paste
What subscription do you have?
Individual Plus
What platform is your computer?
Debian GNU Linux 7.1.13+deb14-amd64
What issue are you seeing?
- Codex usage on Plus isn't presented in a unit a customer can independently understand or audit. “5h limit” describes the rate-limit window, not five hours of usable Codex time, while actual consumption varies according to an opaque compute calculation. That makes it impossible to know in advance how much Codex the $20 subscription actually buys.
- There also isn't a straightforward higher-capacity individual subscription between Plus and the substantially more expensive alternatives. Please provide transparent usage units and an individual upgrade option for heavier Codex users.
What steps can reproduce the bug?
Feedback ID: no-active-thread-01a0971a-1833-7dc2-8eb9-8f8b118ff59d
What is the expected behavior?
Reasonably transparent billing. An upgrade option from personal plus to something less than $100/month.
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
No repository files, tests, or entry points are mentioned. Start by determining whether this repository contains the Codex usage and subscription surfaces described in the issue. Done would require a maintainer-defined, implementable scope for transparent usage units and an individual upgrade option.
Written by the indexing model from the issue text.
Assessment
- Domain
- payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100