r/coderabbit • • 1d ago

Discussion & Feedback AGY / CODEX

Hey everyone,

I’m a solo developer working on a medium-sized project, and I’m looking for advice on how others handle their code review workflows when relying heavily on AI coding agents.

Right now, I’m paying for CodeRabbit, but I’m considering canceling my subscription. My current workflow involves generating code with Claude Code and then using Codex and the agy CLI (Antigravity) to review the output before merging.

Before I decide to cancel CodeRabbit, I’d love to get your feedback on a few points:

  • Redundancy vs. Value: If you already use multiple agents to cross-check each other (e.g., having Codex or Antigravity review Claude Code's work), do you find dedicated PR review tools like CodeRabbit redundant?

  • Review Blind Spots: Are there specific issues—like subtle regressions, security flaws, or broader architectural context—that CodeRabbit catches on pull requests that CLI agents tend to miss?

  • Your Solo Setup: How are other solo devs structuring their AI review loops to balance cost, speed, and code quality?

Thanks in advance for sharing your setups and opinions!

2 Upvotes

7 comments sorted by

1

u/juanpflores_ CodeRabbit Staff 1d ago

Running Claude Code, Codex, and agy over every change can get expensive pretty fast, and in my experience stacking more models mostly gets you the same findings several times rather than deeper ones. A dedicated reviewer is built to look at the whole PR with repo context and learn from your feedback over time, so it doesn't just give you another pass from a different model.

I'm curious what's pushing you to switch, though. If something isn't working for you, I'd like to know.

1

u/Some_Balance_1689 1d ago

I am catching a lot of issues thanks to this approach, and I was wondering if should I keep my code rabbit subscription.

1

u/rlorenzo 1d ago

I use Claude primarily and have agy and sometimes gave Codex review using this loop

https://github.com/rlorenzo/ai-coding-setup/blob/main/bin/code-review-loop

But Coderabbit still finds valid issues. It’s a nice safety net.

2

u/Some_Balance_1689 1d ago

Thanks for sharing it.

1

u/Some_Balance_1689 1d ago

That is a really neat setup! My workflow is slightly different: I installed Codex and agy locally on my machine, then I just prompt Claude to call both tools through its terminal integration. It keeps everything unified and runs smoothly without needing to juggle several separate interfaces.

1

u/Shep_Alderson 1d ago

I’ve been using CodeRabbit for several months, after testing it against Greptile and Macroscope. CodeRabbit used to be really good, but I’m guessing they are losing too much in token API costs and that’s why the rate limits have gotten so strict. I’ve been seeing too many “rate limited, on demand could cost up for $XX.YY for the review” and I’m sorry but only getting 1-2 review passes a day and having to pay tens of dollars or more for each review to perform additional reviews, it’s just not worth it.

What I decided to do was take some of the Fable 5.2 usage (and usage resets they gave us for Fable) to make a review agent skill of my own. I had Claude Code review all my repos and their PRs, scrape together details of every issue that was found, untangle and dedup the findings, and lump them together into “classes” of bugs I could make “generic” prompts for checking for. I had Claude Code make the prompt, then test it against a “PR” consisting of the code checked out with a single additional commit for the “diff”, then run the prompt to see if the subagent finds the same issues without seeing any of the other code nor GitHub history. I then had Claude tweak the prompt, while keeping it generic, to increase the findings until it found all the same issues that CodeRabbit and Codex found. I then had it do another test “PR”, tweak, then back test on the previously tested “PR” to ensure no “regressions”. I kept doing this over 5 different “PRs” until I eventually had a collection of 4 prompts that look at code from different angles and could one shot find all the same issues as CodeRabbit and Codex combined. I’ve since tested it with multiple models and it tends to catch most or all issues, as long as it’s a decently recent model.

I plan to publish this as a skill once I get it polished up a bit. I’ve already cancelled my CodeRabbit plan. It was good while it lasted but isn’t worth it anymore.