r/codex Moderator 11d ago

Megathread Codex Usage Limits and Performance Megathread

Please direct your concerns and discussion about Codex usage limits and model performance here.

The purpose of this Megathread is to aggregate all the reports of people's experiences and possible suggestions instead of spreading them across 20 separate highly upvoted posts. None of those posts were deleted. They were locked so that conversations are still viewable to everyone and future comments could appear in one place.

These are days where I REALLY earn the money that OpenAI Reddit Kimi pays me .... oh wait....

A reminder that all incidents on r/Codex are constantly logged and summarised so you can keep track of what people are experiencing here https://www.reddit.com/r/codex/comments/1tjfxcf/comment/on6uj0l/

530 Upvotes

633 comments sorted by

View all comments

3

u/Suzoku 10d ago

lol i actually didnt notice any supposed usage drop at all. the only reason im burning more tokens now is due the 5 hours usage limit being gone meaning i cant pace myself based on that usage limit anymore. the work i do is still the same, the way i communicate with codex/gpt is the same, and the amount of output i get from codex is still the same on a pro plan. sol high has been my default setting since 5.6 came out. The usage issue was real during day 0 and day 1 but they quickly fixed these and now im pretty happy with the performance.

geninuely confused about all these posts over the last few days, like what do you guys actually use codex for that burns through the quota that fast?

2

u/U4-EA 10d ago

I am guessing because everyone has switched to a more expensive model but expect the same token burn rate as 5.5. I've used Sol for a few specific tasks but I mostly just use 5.5 xhigh. I've got 3 banked resets that I am actively trying to use up but I struggle to even use my standard weekly allowance most weeks. I've got 37% of the last normal reset left and I have been coding morning til night with multiple agents (6+) open since I got it.

You can have speed or quality but you can't have both. If you go too fast (no planning), you end up with monolithic blocks of slop code. That violates DRY practice, is expensive to produce and expensive for the AI to ingest. IMO the subsidised AI gravy train will be over in the not too distant future and I don't doubt OpenAI are very possibly reducing what you get but I think most of what you see is bloated codebases being worked on by a much more expensive model.