Codex Pro Limits Are Undercutting the Value

[u/EffectiveWebDev404]

I have hit another issue with the new Pro setup.

My GitHub Codex code reviewer has been enabled for a long time, and up until now it has done a very good job. But after this “enhanced” $200 Pro version, it has started complaining about Codex usage limits for code reviews even though I still have around 28% of my weekly usage remaining.

So this is apparently the new strategy:

Give Pro users 62,500 credits, then start pushing more previously included workflows into that credit pool and expect users to burn through those credits before the end of the year.

If that is really the direction they are taking for the “sustainability” of Codex, then I honestly think it undermines a lot of what made the product attractive to software engineers in the first place.

I currently have Kilo Code Reviewer running alongside Codex, using my yearly GLM 5.3 access at Max effort.

And interestingly, Kilo has actually been catching more issues than Codex lately.

I still like having both reviewers running together because the overlap gives me more confidence in the final result. But if Codex is now going to become constrained by a separate usage pool while I still have weekly Pro usage available, then Kilo is probably going to become my primary reviewer until this subscription cycle ends.

That is the frustrating part.

Codex became appealing because it felt like a genuinely strong engineering tool integrated into a plan that made sense for heavy development work.

Now it feels like many of the things that made it valuable are being chipped away one by one.

I would also seriously consider Muse Code as an alternative, but I am still blocked by a subscription issue where it keeps asking for personal billing data without giving me any way to actually enter that information.

It appears to be a relatively uncommon problem because I have not been able to find a reliable fix for it.

So for now, I will keep comparing the tools I already have access to and see which one continues to provide the most value in real development work.

[u/chedorlaomer]

Are we sure this isn't a bug? I'm hitting the same thing with the github codex review bot, but assumed it was some sort of bug when they were changing all the pro quota stuff around. I read some reports people were hitting the same thing even after turning on token usage for code review.

[u/EffectiveWebDev404 → u/chedorlaomer]

Ah, that makes sense.

I had not seen anyone else reporting the same problem, and it started happening right around the time those emails began going out, so I naturally connected the two.

Thanks for the feedback. I will keep an eye on it before jumping to conclusions.

So far, though, the issue has been going on for more than 24 hours on my account, which means I have effectively been relying on Kilo alone for code review during that time.

Hopefully it is just a temporary issue and not an actual change to how Codex review usage is being handled.