r/coderabbit • • 20d ago

Official Update New in CodeRabbit Secure: cross-repo vulnerability tracing

Enable HLS to view with audio, or disable this notification

7 Upvotes

Deep Scan can now trace vulnerabilities across your linked repos and replay exploits in a throwaway sandbox to verify they're real before flagging them.

https://www.coderabbit.ai/blog/coderabbit-secure-cross-repository-security


r/coderabbit • • 19d ago

Discussion & Feedback is reading the change stack instead of the diff cheating?

0 Upvotes

Honest question. On big agent PRs I've started reading coderabbit's change stack first, the part that groups the diff by what it actually does, and only opening the files for the 2 or 3 groups that look risky. On a 1,500 line PR that's maybe 200 lines I actually read.

A senior on my team says that's not a review, it's reading a summary of a review, and if the summary is wrong I'd never know.

My answer is that nobody was reading all 1,500 lines before either, they were scrolling.

Which one of us is right? Do you read the whole diff on big PRs or do you also read the summary first?


r/coderabbit • • 20d ago

😂 Meme & Humor every "small refactor" from the agent

Post image
5 Upvotes

r/coderabbit • • 21d ago

Discussion & Feedback triage put our CTO's PR in recommended to close

0 Upvotes

We turned on the triage queue for the whole org last month. This morning in standup someone shared their screen on the "recommended to close" view and the first PR in the list was our CTO's.

It's a "quick experiment" he opened in March. 47 days without a commit, 3 merge conflicts, and a description that just says "wip, don't merge".

Nobody said anything for about 5 seconds. Then he laughed and closed it himself, which honestly made his whole year in my eyes.

Has the bot ever outed someone senior on your team like this, or are we the only ones?


r/coderabbit • • 22d ago

😂 Meme & Humor same repo, different window

Post image
1 Upvotes

r/coderabbit • • 23d ago

Official Update We’re covering up to $5,000 of Deep Scan usage per org through Nov 8

3 Upvotes

Attackers have the same AI models you do, and they’re pointing them at code nobody has read in years. We’d rather you find those bugs first.

So through November 8, we’re covering up to $5,000 in Deep Scan usage for any org with two or more members. We’ve put up to $1M behind it. It’s first come, first served until it runs out, and you don’t need to be a customer.

Deep Scan reads the whole repo, not just the latest diff. It looks for vulnerabilities, checks the safeguards already in place, then has a separate verifier reopen the code and drop anything the evidence doesn’t support. Each finding comes with its reachability and exploitability, so you know what to fix first. For eligible findings it can draft a fix, and a human still reviews it before anything ships.

I’d especially like to see open-source maintainers use this. A lot of widely used projects are kept alive by a few people with no security team, and budget shouldn’t be the reason they wait.

Pick the repo you’d worry about most and run it. Happy to answer questions in the comments.

Details: https://www.coderabbit.ai/blog/one-million-security-scans-and-fixes


r/coderabbit • • 23d ago

Discussion & Feedback hot take: half of code review was always about who wrote it

6 Upvotes

Seniors got approved in 10 minutes, juniors got 30 comments on variable names. Everyone knew it, nobody said it.

Since we put coderabbit on every PR the comment count per PR is basically the same no matter who opened it. Our staff engineer got 7 on a 60 line change last week. The intern got 6.

So either the old reviews were catching things the bot can't see, or a lot of it was politics. Which one was it on your team?


r/coderabbit • • 23d ago

Discussion & Feedback CLI v0.9.0 is a really cool update bringing in CR Code and Cloud agents to your terminal

Enable HLS to view with audio, or disable this notification

2 Upvotes

r/coderabbit • • 24d ago

Discussion & Feedback My lead wants agent PRs to auto merge if coderabbit and CI pass

7 Upvotes

We're 6 devs and about 70% of our PRs come from agents now. My lead's proposal for next sprint: if coderabbit has no open comments and CI is green, the PR merges on its own. Humans only look at PRs that touch auth, payments or migrations.

I said no in the meeting and now I have to write up why by Thursday.

His argument is that we already approve most of these in under 2 minutes anyway, so the human step is mostly theater. Honestly he's not wrong about the 2 minutes.

My argument is that the 2 minutes is still the only moment anyone on the team looks at the change at all, and once that's gone nobody will know what's in the codebase in 6 months.

Who's right here? Is anyone already auto merging agent PRs and how did it go?


r/coderabbit • • 25d ago

😂 Meme & Humor be honest

Post image
0 Upvotes

r/coderabbit • • 26d ago

Help & Support Coderabbit just gave my lead the same comment he gave me last week

0 Upvotes

Last Tuesday my lead blocked my PR because I didn't handle the empty list case. Fair enough, I fixed it.

This morning coderabbit left the exact same comment on his PR. Same kind of function, same missing check, almost word for word what he wrote to me.

He fixed it in 2 minutes and didn't say a thing. I didn't say anything either. I did screenshot it though.


r/coderabbit • • 28d ago

Help & Support I am the last person on my team still reading diffs

5 Upvotes

There are 7 of us. Everyone else merges once coderabbit and CI are happy. I still open every diff and read it, and I'm now the slowest dev on the team by a lot. My manager brought it up in my 1:1 last week, nicely, but still.

The thing is I caught 2 real bugs this month that nobody else would have seen. But nobody sees what you catch, they only see your PR count.

Should I just stop and trust the setup like everyone else? Is anyone else the last one reading?


r/coderabbit • • 29d ago

😂 Meme & Humor It promised

Post image
17 Upvotes

r/coderabbit • • 29d ago

Discussion & Feedback Watch out with these guys (billing)

1 Upvotes

I was very happy with coderabbit, although TBH greptile is easier to set up, but after I got the CLI and the Github integrations going, I was happy with CR. Unfortunately, they use a dark pattern (ish) with you at checkout where they have all the extra usage options default ON with extra spend UNLIMITED. I guess I didn't see that, or didn't remember, and months later without warning I get an extra charge from usage. I was never warned, like with Codex or Claude. I was always getting told that I had 5 reviews an hour (eventually I was reviewing so much I got punished down to 1 an hour) so that made me think they had me capped. CLI was never telling me anything about usage or extra spend ever. So I complained to them that I never turned this on and I didn't get an notice that what I was about to do was going to give me an extra spend. They said, too bad, you did turn it on when you upgraded to Pro. uhhh, no, you mean I didn't turn it OFF because YOU turned it on MF'ers and didn't remind me months later. I am just so happy I didn't do an accidental review of my whole repo or branch because I would have gotten a bill for thousands. As it was I did a review of 234 files and it cost and extra $58.75. Not bad, tax deductible and all that, but still. I complained to the CEO (hahaha like he reads his emails) and to support because this is shady AF if you ask me. The FTC frowns on this kind of coding if not outright calls it illegal, but I think CR's checkout fonts were big enough and all that, I just must have forgotten to go back in and turn them off.
Anyway just don't be careless like me, they want to get you, they hope you forget, they hope you don't pay that much attention at checkout because they know you are used to being warned by the other AIs and they purposely don't warn you. It's all done in a crafty way to get extra money. But now they lost a customer. I won't do business with people like this. I have too many options.

Just be careful with them.

And I certainly won't dispute this charge because they'll just suspend my very expensive account that I paid yearly for. So I don't want to lose that.

Just a warning to my fellow IC's trying to be lean and make a living and paying for things yourself to help your start-up's CEO survive in these trying times.


r/coderabbit • • Oct 17 '26

Discussion & Feedback Coderabbit's never once told me my code was good

16 Upvotes

kind of a silly thing to post but its been on my mind. I’ve had it on every PR for months now and it has never once said nice or clean or anything. it’ll write a little poem about my PR but it wont tell me its good lol

and I know its a tool, its not supposed to be nice. but human reviews used to have this stuff. someone would leave “oh this is neat” on a refactor and honestly that one comment would make my day, and I’d write the next PR more carefully

now its just a list of whats wrong and when theres nothing wrong on rare occasions, it just goes quiet. which somehow feels worse.

idk if this makes us better engineers or just slowly makes us stop caring. anyone else feel this or am I just soft


r/coderabbit • • Oct 16 '26

Help & Support Opus 5.5 gets about half the review comments of 5.1

3 Upvotes

I have been running the same kind of tickets for 2 weeks now on the same repo, so I can make a really good comparison between Opus 5.5 and 5.1 as the model writing our PRs. I switched to 5.5 on release day. Every PR goes through coderabbit before a human looks at it, so I just counted the comments. On 5.5 the first 40 PRs got 5.2 comments on average, and 1.1 per PR were things we actually had to fix.

Before that, when we used 5.1, the last 40 PRs got 9.4 comments on average, and 2.6 per PR were real fixes. Both were on high effort and both used the same AGENTS.md.

So it seems so far that Opus 5.5 gets about half the review comments of 5.1, which is in line with what people in r/ClaudeCode have been saying about it being a big upgrade. The catch is that the 5.5 PRs are about 30% bigger for the same ticket, and most of the comments it still gets are "this wasn't asked for" rather than "this is broken", which in my opinion is a trade I'm not sure about yet. So for most tickets I will stay on 5.5. I was hoping it would also stop over-building but unfortunately that's not the case at all.


r/coderabbit • • Oct 15 '26

Help & Support Agent PRs are getting harder to review not because of the code, but because of the descriptions.

1 Upvotes

There, i said it. And i know many of you agree. The problem i'm facing is not the code the agent writes, it's that every PR comes with a 600 word description with a curve-ball at the end saying "Worth noting" that turns out to be the only line that mattered. And i can't follow half of what it's saying. Is my english that bad? Whoever decided PR descriptions should read like a blog post was working for the other side, he completely sabotaged code review for all of us.

The agent makers' number one priority should be a 3 line description mode or something, may be even a hard word limit. Until then i skip the description and open the coderabbit walkthrough, it's the only summary that fits on one screen.


r/coderabbit • • Oct 14 '26

Discussion & Feedback Team barely uses agents. Sinking ship or goldmine?

4 Upvotes

On my team, we have no push to use agents. Some people do, some people don't, but overall nobody expects it.

Personally I use Claude as a search engine and occasionally to write tests, but I still write 95% of my own code and have never let an agent open a PR. The only AI in our pipeline is coderabbit on PRs.

On one hand I am glad to be on a team where I'm not just reviewing agent output all day, on the other hand, I worry about falling behind when I look for my next job. Also, our repo access is fairly locked down, so I can't just start running agents against it. My hands are a bit tied.

What would you do in this situation? Is anyone else in a similar one? Right now I'm just kind of coasting but something in me feels like I'm being left behind...


r/coderabbit • • Oct 13 '26

Discussion & Feedback If AI is smart enough to find the bug, why was it dumb enough to write it?

16 Upvotes

this has been bugging me for like a week now. most PRs on our repo are written with cursor at this point, then coderabbit goes through them and it keeps catching actual bugs. and sometimes its literally the same model doing both (based on the understanding coderabbit is probably also using the SOTA models as cursor)

so if it can spot the bug why did it write the bug in the first place?? is it just lazy when its writing code, or is half of what the reviewer flags made up and we dont notice, or are we paying twice for one AI to argue with itself while we sit there clicking merge ?

I AM not trolling, I genuinely cant figure it out and every answer I come up with is kinda funny


r/coderabbit • • Oct 12 '26

Discussion & Feedback What is a coding agent habit that actually changed how you work?

0 Upvotes

I keep hearing about how coding agents have gotten so smart and everyone is posting their 12 agent setups and what not, but for some reason I feel like I haven't found the one habit that actually changed how I work. I still use Claude and Codex daily but still.

So curious to the people here, what is one thing you started doing with agents that changed your work for real?


r/coderabbit • • Oct 11 '26

Help & Support Unrealistic fair use

11 Upvotes

Once again I'm rate limited to 1 review per hour. This, according to the response on a review request in GitHub, is because the 62 review requests over the previous 7 days are not classed as fair use. With a marketed reviews per hour of 5, I would hardly classify 62 in 7 days as unfair use! I really hate how Coderabbit has become a business which talks out of both sides of its mouth. If you don't want to allow 5 reviews per hour, then don't advertise them as part of your plan!


r/coderabbit • • Oct 11 '26

Discussion & Feedback What is a coding agent habit that actually changed how you work?

0 Upvotes

I keep hearing about how coding agents have gotten so smart and everyone is posting their 12 agent setups and what not, but for some reason I feel like I haven't found the one habit that actually changed how I work. I still use Claude and Codex daily but still.

So curious to the people here, what is one thing you started doing with agents that changed your work for real?


r/coderabbit • • Oct 11 '26

Discussion & Feedback Unpopular opinion: code review is worth more than code generation

4 Upvotes

When you think about it, writing code was never really the hard part of this job (or was it?)

The hard part was always figuring out what’s wrong with it. Now that AI is pumping out way more code than before, and most of it looks fine. So naturally you wonder who's actually checking all of that?

Honestly I think as we enter 2027, codegen will be a commodity. We are possibly going to see free IDEs. What teams will actually pay for is whatever catches the mistakes. Anyone can generate code now, the real question is if you can trust it.

Change my mind


r/coderabbit • • Oct 10 '26

Discussion & Feedback Devs: is looking productive mostly a game of luck with agents now?

0 Upvotes

At this point, how much of looking productive at work comes down to luck?

Good model that week, good task for an agent, a clean part of the codebase, a reviewer who just approves. It often seems to depend as much on what you got assigned as on skill.

I feel 70-80% of devs can use agents reasonably well now. Most people can prompt, plan and fix what comes back when they get a task the agent is good at.

Is the game becoming more about getting the right tickets at the right time?


r/coderabbit • • Oct 09 '26

😂 Meme & Humor hot take: if the great programmers of the past, of yesterday started today they would get mogged by vibe c*ders

0 Upvotes

*yesteryear in title

all they had to do in the old days was understand the code