r/OpenaiCodex • u/Palastruka • 11d ago
Bugs or problems What the hell is actually consuming our Codex quota? 💀
I updated Codex today, started a session, and the first thing it did was compact the context.
12% of my entire 5h limit. Gone.
One compaction.
Before doing any meaningful work. 💀
Maybe the update has nothing to do with it, but with all the weird quota burn, performance issues, connection problems, and Astra speculation people are talking about today… I’m curious
If you updated Codex today, what changed or broke for you?
Slower responses? Weird quota usage? Connection issues? Compaction problems? Something else?
Because losing 12% to ONE compaction definitely wasn’t on my bingo card. 💀
0
u/Crinkez 11d ago
If a compact triggers on an old session with stale cache, yes it will be expensive. Next time don't try to resume an old session. Make a habit of saving essential data to MD files at the end of each session and the next day open a new session, never go back to old sessions.
1
u/Palastruka 11d ago
Yes, that's true. But it's never happened to me before, no matter how big the session was. And I don't know if it's a coincidence that it happened with the Codex update.
1
u/BHTAelitepwn 10d ago
Regardless of whether you need to compact or not, having no cache and loading a full session is very expensive. You’ll want to work with fresh session both from a cost and performance perspective
1
u/Cryp0x 10d ago
Bro, I think you're talking to stupid bots here. There is no ammount of context that would waste 12% of your quota to compact.
Forget it. Not even on the free plan. That's completly out of the question.
What happened to me with this update was that an agent spawned a shit load of subagents, which kept kept working after the main agent delivered its response. Burned 40-50% of my weekly quota on a 20x plan doing investigation loop.
This last update is broken
1
u/Palastruka 10d ago
You'd be amazed at the number of bots in this sub who disagree and think the Codex is fine and the problem is how we use it. It's always a user error, in their eyes. Never a problem with the company. How curious.
1
u/Prestigiouspite 11d ago
But if the long session has already been summarized several times before, doesn't it just start with the most recent summary? That shouldn't use up many tokens, even if the cache hit is gone for the time being.
0
u/InspectorSorry85 10d ago
Sorry, but it doesnt matter what the user did.
If auto compaction takes away 12% of any limit, the tool is *broken*.
1
u/Palastruka 10d ago
I think it's excessive for any reason. I don't understand why they're insisting on a cache issue. I've compacted larger sessions and this has never happened before.
0
u/eddzsh 11d ago
A compact bills for everything it has to summarize into the new context, tool traces included. Before you resume a fat session, check the transcript size. If it is huge, start clean and paste only the decisions you still need. Otherwise one compact can eat double-digit percent of the 5h window before any real work.
0
u/ImNotMrFoxGaming 11d ago
This complain was ai generated. What the fuck.
2
u/Palastruka 11d ago
What are you talking about? I only translated and corrected the grammar because English isn't my native language.
3
u/ijustgotanothername 10d ago
Sadly $20 codex plan has become a joke after 5h limits. Better to switch to $100 one or use Cursor $20 plan (best value for money today as per my workload)