So the core concept of your message has been addressed.
You’ve been advised on what you can do to make the codex usage last longer.
Have a good day.
I’ve noticed the 5h limit seems incredibly low compared to any other week. I’ve been using Codex since it’s launch in February and am very aware of the 2x limits that just expired. Even so, I was fairly happy with how much usage I got out of a $20 plan. Today, asking to summarize a single method to verify if the pre-multiplication was working as intended used 6% of my 5h usage. It didn’t code anything, or read large files, or even work in a giant repo.
I followed up with a simple prompt to modify the single method, and it took another 5% of my usage out.
I’m not sure if it’s a bug or what, but this is the first time I’m logging into the forums to even say anything, as it’s really bad today. Hopefully the OAI team can figure out what’s going on, as at this level, I’ll get about 10-15 minutes of usage before the 5h timer is up even in a small single app project with a dozen class files.
1 Like
Stop replying to that useless troll please and just mute him so you don’t get notifications for his useless spam trying to provoke rage reactions from people affected by the issue. Literally everything he says in many threads I’ve seen is useless, ignorant, uneducated ramblings. He gets his kicks from trolling people, don’t give him the satisfaction and ignore him.
2 Likes
I already know that workflow. I’ve used Codex that way too, and I still do when it makes sense.
What you keep framing as some deep insight is really just a basic workaround. A lot of people understood that from day one. The difference is, not everyone is using Codex for tiny edits, simple scaffolding, or toy-level tasks. Some of us are using it for heavier technical work, where sustained iteration matters and the current limits become a real constraint.
So no, this is not about me being vague or not knowing how to prompt. It’s about you assuming your lightweight usage pattern applies to workloads where it clearly doesn’t.
And the patronizing tone doesn’t help your argument. It just makes a pretty shallow point sound more important than it is. I know the workaround already. I’m saying it’s not enough for the kind of work I’m actually doing. If a product only feels “good” when people narrow their usage and push the rest somewhere else, that’s a product limitation, not user error.
2 Likes
Ok boss.
Ive used it nonstop for days, almost every waking moment on 2 pro accounts an not had any issue.
planning seems to be key man.
So I can agree with that, my experience is also with GPK 5.4, it doesn’t matter if you work with low or high, it doesn’t matter, at just under an hour, 5 hours are over and whether you work with low or high reasoning, when the model says I don’t need the power, it doesn’t matter if it’s longer or shorter, it doesn’t make a difference. In the real software development area, just a few minutes, if you differ from low to high reasoning, so you can always run on high, I’ll probably run the days on extra high and see if extra high also lasts about 45 to 60 minutes. And the other recommendation, for example, to switch to 5.4 mini is also pretty banana, because 5.4 just produces less cool results and you need longer and it just doesn’t work for you, so the only option is to switch to 5.3.
1 Like
5.3 doesn’t make a difference. My metrics are with 5.3 high already, trying to get the most effective usage. Anything less than 5.3 high makes so many more errors that it normally does that I need either to spend a half an hour after each small task to fix it by hand or burn more limits for the same task – and still having to fix issues manually afterwards anyhow 99% of the time (that’s on C++ tasks, YMMV with simpler workloads).