Rate limits for code review on plus tier leads to unlimited snowballing

[cozuya]

The bigger a PR gets, the more "code review currency" it consumes. This is pretty obvious, but the problem is really that you can never catch up. Its probably a bad problem to have, but I'm so productive that my PRs are now so big that they use up literally my entire weekly CR tokens, for just one of them. So what happens is I make a PR right about when my tokens refresh, and when they do, I spend almost all of my tokens just on the one @codex review and its followups to get it to sign off. And then next week my next PR is bigger and more complex, and it takes more of my tokens, and so on.

You'll probably say "make smaller PRs", but in my experience that won't really help, I'll still burn tokens too fast. This is a bit of a surprising result seeing as for the other bucket heavy usage doesn't snowball in this way at all - code review is a gulp, general usage is a sip.

(fyi for my use case, these are not traditional feature specific PRs this is just "work" on a not-in-prod-yet greenfield project that I'm the solo dev on, stuff that should be merged to main because its done for now)

[etraut-openai]

I'm glad to hear that you're getting such a productivity boost from Codex!

If you need additional capacity for code reviews, you can upgrade to a pro subscription. If you don't need that much capacity, you can buy additional credits and apply them to your plus subscription.

Another option is to use the /review slash command locally rather than use cloud-based code reviews. The local /review usage comes from the same "bucket" of credits as your normal code generation usage.

[cozuya]

Thanks, but as I'm sure you know thats not as good. Please consider bringing up this problem, as I doubt you really want an entire bucket of code review tokens (and more) burned on one PR every week for people like me.