Burned through 6% usage in 90 minutes
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)?
Version 26.814.41407
What subscription do you have?
20x
What platform is your computer?
MacOS
What issue are you seeing?
I am burning through a shocking amount of usage in 90 minutes. 6% of my weekly and I dont feel Ive done particularly taxing tasks. WHen I asked Codex the reply said I had sent up an unusually large amount of data - but it was a single comment of "How can I be down 6% of my daily tokens already? Ive only been working for 90 minutes.".
On further questioning I got:
You’re correct: your prompt was tiny. I described it poorly.
What I received alongside it included app/runtime context such as:
- System and developer instructions
- Your workspace’s AGENTS.md
- Environment and permission details
- The installed-skill and tool catalog
- The recommended-plugin catalog
- Workspace memory guidance
You did not type that material; Codex attached it automatically. OpenAI’s documentation confirms that prompts, chat history, files, tool results, and AGENTS.md content can all consume tokens. It also notes that cached input is charged at a substantially lower rate. Official usage documentation
However, I cannot see your account’s detailed usage breakdown, so asserting that this task’s attached context materially caused your 6% consumption was unjustified. It could instead reflect earlier tasks, model/reasoning choice, tool activity, output tokens, or shared ChatGPT Work usage. My earlier explanation presented speculation too confidently.
What steps can reproduce the bug?
Feedback ID: 01a0203f-c3ee-7f50-9226-7dff3303db17
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
The report names no source file, test, or entry point; start with feedback ID 01a0203f-c3ee-7f50-9226-7dff3303db17 and the Codex App version and platform details. Done would require a reproducible explanation of the unexpected usage consumption or a confirmed fix, with the expected behavior specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100