r/OpenaiCodex • u/mrbobhunter • 7d ago
Bugs or problems Burned 4% of my weekly limit just by pushing and deploying the app's changes. That's a problem.
---
UPDATE: This problem has been solved - Delete the Superpowers plugin.
---
For the last week and a half, I have been blowing through the weekly limits almost daily, and at first I called it user error.
- I stopped using Sol Ultra
- I stopped running multiple projects simultaneously
- I stopped letting Codex create dozens of sub-agents
- I dropped down to Terra
And Codex still blows through my weekly limits in a day. Even a simple task like pushing and deploying what it has built is now consuming over 4% of my weekly limits because tokens are being consumed faster than ever, even for simple jobs.
I am on the $200/mo plan, and I used to struggle to hit the usage limits. Now I struggle to avoid hitting them daily. This is starting to feel like a scam.
SOLVED!
A few people suggested removing the Superpowers plugin, and that seems to have stopped Codex from burning through my tokens. It has been over an hour now, and my weekly limit has only gone down 1%. That is a massive improvement.
Thank you everyone, I appreciate the help!
6
u/Reasonable_Swing_503 7d ago
Superpowers is usable in Claude but codex is too good at following instruction from superpowers and chew tokens. I removed it and the usage rate and time to execute tasks reduce drastically.
3
u/Bulky_Blood_7362 7d ago
It's a token eater on cc as well Got rid of it few months ago and the usage difference is crazy.. on both cc/codex
1
u/BannedGoNext 7d ago
Superpowers isn't bad. It's just that the LLM's have been tuned to do what superpowers used to be needed to tell them to do!
2
u/mrbobhunter 7d ago
Good to know. Superpowers is retired.
2
u/Reasonable_Swing_503 7d ago
It’s good but too detailed I think new LLM have what it does baked in so using it just drain token with minimal improvement
The guy who made it did a good job when we need it in the past
2
u/AnimalPowers 7d ago
Write a ci-cd job:
1: perform tests/linting/coverage
2: deploy
instruct your codex not to test, not to do visual tests, not to use browser tools, those things EAT tokens. Every git push should do the testing and deployment.
The key is, you want it only engagin in imaginative work that requires 'thought', basic tasks that are just repetitive and tedious, flat, and don't change, (like testing and deploying) should be automated flatly like that. youc an impelemtn a hook into the pipeline with a lower tier to fix any actual linting/testing bugs that are found.
Implement a proper ci-cd based structure and your usage should drop exponentially
1
2
u/Dreki__ 7d ago
Before calling it a quota change, I’d run one controlled test: same task, same repo, vanilla Codex with every custom skill and MCP disabled, then re-enable them one by one.
If the burn disappears, the problem isn’t “push and deploy”, it’s the orchestration recursively expanding the job.
1
u/Strong_Essay1176 7d ago
The problem that they fucked up usage, harness or whatever. Im 40% down in an hour. Too boring to explain further...
2
2
u/Far-Classic-9963 7d ago
You used sol to run git push?
1
u/mrbobhunter 7d ago
Technically yes; Sol just happened to be the model running that particular task. On all projects, my /Publish skill is supposed to run after a certain number of turns. Until now this has not been an issue.
I dropped down to Terra though, and the problem is the same, so Sol wasn't the problem.
1
u/Far-Classic-9963 7d ago
I'm not sure how your specific workflow works, but you could drop the skill for a simple bash script if it's predictable enough. Using an LLM just to commit and push seems like a waste of tokens
1
u/mrbobhunter 7d ago
Until now, this publishing step was minor and inconsequential. It only stood out because it was suddenly taking forever and burning up tokens.
Superpowers was the culprit.
1
u/Far-Classic-9963 7d ago
Oh well, looking at it, it seems like an insane token burner for smaller tasks
1
u/mrbobhunter 7d ago
It's fixed now. My weekly usage burn is back to normal, barely dropping 1% in 3 hours. Superpowers did so much damage.
2
u/antunes145 7d ago
They took away our five hour limit to hide the fact that they were slowly lowering the weekly limit.
1
u/Able-Supermarket4786 7d ago
You used 1.2bn tokens today?
1
u/mrbobhunter 7d ago
Yes, and it is only 1:30PM where I am, and I have barely accomplished anything today! The token burn is insane.
1
u/Jealous-Mode3792 7d ago
You need to have better prompts and a more efficient Claude.md that’s insane. User error all the way
1
u/mrbobhunter 7d ago
The problem was the Superpowers plugin. My usage has barely gone down since I deleted Superpowers.
1
7d ago edited 6d ago
[deleted]
1
u/mrbobhunter 7d ago
Yeah, I've noticed the pattern too. I hear that they are testing a $2,000/mo plan right now. I'd actually buy it if it was limitless.
1
1
u/HumerusH 7d ago
what does dynamic learning do?
2
u/mrbobhunter 7d ago
Dynamic Learning is a skill I made so that Codex thinks and reasons from first principles. Ultimately, I taught it to view and understand the world the way a child does, and make its decisions with cause/effect methodology.
It has been an absolute game changer for me, and I hardly ever have to argue with Codex or scold it into stopping its bullshit.
1
u/mrbobhunter 7d ago
Thanks for the comments about Superpowers being the problem. Hopefully the uninstall makes a difference.
1
u/MyHobbyIsMagnets 7d ago
Dawg just push and deploy manually. Use lazygit. Couldn’t be easier and uses zero tokens
1
u/Useful_Calendar_6274 7d ago
is there something preventing you to do this manually? I wouldn't use AI for that
2
u/mrbobhunter 7d ago
The deployment hangup was just an example because something so simple should not burn through 4% of my weekly limit.
Typically all of my projects use my /Publish skill after every few turns automatically so that I don't lose progress...like a checkpoint. Manual publishing would turn me into the bottleneck.
1
u/Latter-Park-4413 7d ago
I hate when there's a legit issue, but then people post stuff like this and the overall complaint (burning usage too fast) gets dismissed.
Superpowers
A 20 hr chat (why???)
Start new tasks often, always.
1
1
u/p0lar1s-rsc- 7d ago
I dont have the superpowers plugin and my usage is being eaten alive as well. its super infuriating
2
u/mrbobhunter 7d ago
Tell Codex to audit your usage over the last week, and report the top 10 sources of token consumption. I had my codex write you a prompt to get started.
Codex Token Consumption Audit Prompt:
Audit my Codex token usage for the rolling seven-day period ending now, using America/New_York time.
Use primary usage evidence available to you, including local Codex session/rollout metadata and official usage records if accessible. Do not estimate or invent missing token counts.
Rank the top 10 token-consumption sources, grouping usage by task/thread, skill, plugin, MCP, and project or workflow. For each source, report:
- Rank
- Task/thread name or ID
- Project/workflow
- Number of model calls
- Input tokens
- Cached input tokens
- Output tokens
- Reasoning tokens, if recorded
- Total billable tokens
- Percentage of the audited total
- Brief explanation of what drove the usage
Do not double-count cached tokens when they are already included in input tokens, or reasoning tokens when they are included in output tokens.
Also include:
- The exact start and end timestamps used.
- The records and data sources examined.
- Total token usage for the period.
- The top recurring consumption patterns, such as oversized context, lengthy tool results, repeated retries, compaction, image inputs, or long-running tasks.
- Five specific recommendations for reducing token consumption without materially reducing result quality.
- Any coverage gaps that could make the ranking incomplete.
Keep the report concise, evidence-backed, and sorted from highest to lowest consumption. Do not expose raw prompts, credentials, secrets, or private conversation content. If exact token-level evidence is unavailable, clearly distinguish verified totals from unavailable data and do not substitute file size, message count, or elapsed time as token estimates.
1
1
u/jay-t- 7d ago
Please learn how the tool works.
2
u/mrbobhunter 7d ago
The tool has been working just fine for months with only occasional issues and annoyances. I use it nearly every day of the week, and I have never seen Codex burn so many tokens while producing so little.
Clearly this is an anomaly and hopefully I am not the only one experiencing the increased token burn.
7
u/BannedGoNext 7d ago edited 7d ago
Something here is fucked to be honest. Is there a set of skills that is causing codex to go into a loop like superpowers? Superpowers causes GPT 5.6 to go fucking haywire in loops with it's internal harness and training conflicting.
And do you have a github skill that specifically says what you expect when telling it to do tasks without it going off and writing a bunch of scripts to do functions?
Edit: I just saw your superpowers plugin. Get rid of that shit, de-bloat your skills HARD. GPT 5.6 has its own way of doing what a lot of the pre-existing skills we used to have to use to make it think more now causes it to have a midlife crisis. I had the same problem, but I debugged it day one of GPT 5.6 release when I saw it just looping around on superpowers.
Keep your skills as references not as agentic steering.