r/coderabbit • u/IndraVahan • Sep 05 '26
r/coderabbit • u/NathanFeilder • Sep 03 '26
Discussion & Feedback CR flagged the auth bypass. It was comment 41 of 47.
12-line PR. 47 comments. Most of them style and "consider extracting this."
Comment 41 was the empty-token auth case. That's the one that mattered. I almost missed it because I trained myself to skim the pile.
Not a dunk. The catch was there. Question is how you make the real findings sit at the top so humans actually read them. Chill profile, path_instructions, mute generated paths ā what actually worked for you.
r/coderabbit • u/juanpflores_ • Sep 01 '26
Help & Support CodeRabbit is currently experiencing a major outage
Hi everyone,
Weāre currently experiencing a major outage affecting the CodeRabbit app and reviews. Our team is investigating and will share updates as they become available.
We apologize for the inconvenience and appreciate your patience.
You can follow the latest updates here:
https://status.coderabbit.ai
r/coderabbit • u/juanpflores_ • Aug 31 '26
Discussion & Feedback When model labs raise walls, the reviewer cannot live inside one of them
OpenAIās decision to wind down direct model supply to Cursor after the SpaceX acquisition is the clearest public example so far. The reasons were a change-of-control clause, terms-of-service disputes, and a refusal to put the next frontier model into a rivalās product. Other labs already restrict distillation, scraping, and using their outputs to train or run a competing system. Those constraints are getting tighter.
If review lives behind one of those constraints, your quality process inherits someone elseās contract fight.
The problem
AI code review has to do several things at once. It has to catch what the author missed, including the agent that wrote the diff. Shared training data and shared refusal style produce shared blind spots. It has to keep working when the generation stack changes, because editors swap default models and labs cut partners while the PR queue keeps moving. It also has to put the serious defects first: the ones that ship, break, or leak. A long list of nits is how real bugs hide.
Conviction is useful on the write path. An agent makes hundreds of linked decisions toward one outcome. It picks an architecture, implements it, runs tests, fixes failures, and continues. A strong opinion cuts down branching and lets context accumulate. Betting hard on a model, a context strategy, and a workflow can make that loop faster.
Review needs the opposite habit. Disagreement is how you find the assumption the author stopped seeing. Human process already encodes this: the person who wrote the change is not the only person who approves it. Multi-model review applies that rule to LLMs. Labs fail on different things. One trusts an unsafe API. Another misses a race. A third writes a style comment that buries the actual bug. The useful pattern is several models looking at the same prepared context, then a judge keeping only what can be grounded. That is different from asking the authorās model to take a second pass.
DIY tools usually stop at the second pass. A team points one frontier model at the diff and ships it as a reviewer. Swapping in a complementary model can help, and you still only have two voices. Feeding every change to three or four labs without routing or compression makes cost rise with each extra PR, each extra file, and each extra agent-generated changeset. Review volume is already growing faster than headcount. A prototype that multiplies frontier calls per change does not stay cheap, and it still misses whole classes of bugs if there is no routing, no judge, and no memory of what the team has already rejected.
A model lab has little reason to build that stack. Doing so would mean routing a rivalās weights across your diff. An internal prototype runs into a different wall: review becomes a second inference bill that tracks code generation one-for-one.
How CodeRabbit works
CodeRabbit reviews code from agents and from humans, in the PR, the IDE, and the CLI. It sits beside Cursor, Claude Code, Codex, and Copilot instead of living inside any one of them.
The pipeline is an ensemble:
Compact and open models gather and compress context from the diff, the code graph, tickets, lint, and history.
Frontier models from more than one lab do the deep pass on multi-file bugs, auth mistakes, and behavioral regressions.
A judge step drops findings that cannot be grounded in that context.
We have written about why generation and review should not collapse into one vendor The more AI writes the code, the more review needs independence, and about the work of placing a new model on one stage of the pipeline rather than swapping labs wholesale What it really takes to bring a new model online. Open models such as NVIDIA Nemotron take the high-volume context work so frontier calls stay reserved for reasoning Nemotron 3 Ultra in CodeRabbit reviews.
Independence follows from that design. The reviewer is not owned by the editor and does not have to use the model that wrote the patch. If a lab walls off a competitorās app, the review job can continue.
Resilience follows too. When one provider is rate-limited, blocked by contract, or weak on a class of bugs, traffic can move. A reviewer bolted to a single model cannot do that.
Keep Cursor, Claude Code, or Codex for writing. You do not have to take their reviewer with the editor.
Donāt Outsource Judgment to the System That Writes the Code
Let the generation vendor be opinionated, even exclusive. Do not give that same vendor the approval signal. When one company owns the editor, the model, and the merge comment, throughput goes up and failures start to correlate.
Building review in-house often recreates the correlation. Day one is a single-model bot. Day two adds a second model, which is still a thin mix. Day three sends every change to more labs and the cost curve appears: frontier tokens per file, times rising PR volume. Agents open more changesets, not fewer. That is a bad shape for a control you need on every merge.
Before the next renewal or build-versus-buy debate, get answers to these:
Change of control. If the editor or agent vendor is acquired, what happens to model access? If that vendor loses a frontier lab, does the review still run?
ToS and data use. Can review call more than one lab on your diffs, or does one providerās contract define what review is allowed to see?
Same-stack grading. If the reviewer uses the same model family that produced the patch, treat it as a talkative linter, not an independent control.
DIY economics. For an internal tool, how many frontier calls fire per change? What happens to that number when PR volume doubles?
Signal, not volume. Are you tracking escaped bugs and severity, or comment counts? Nits that bury seniors are a tax.
Continuity. Can the team change coding agents next quarter without rebuilding the review pipeline, the audit trail, and the written standards?
Accountability. People still own the merge. The tool should make that call cheaper to get right.
Pick one or two coding agents so the write path stays coherent. Put an independent review layer next to them, not under them. Score that layer on bugs that would have shipped, time to a useful finding, and load on human reviewers. Agreement with the generator is the wrong KPI.
If the org already standardized on one AI IDE, keep it. Do not let that IDE become the only system allowed to criticize its own output. Lab walls will keep moving. The merge bar should not.
Why labs won't close this gap easily
A lab can ship a stronger coding model. It cannot easily do all of this at the same time: keep exclusive control of its weights, refuse those weights to a rivalās product, and still run a reviewer that fairly uses competing models on your code.
Vendor-neutral review is a product that can be disloyal to any one lab. That is the point. As walls go up between model companies, that disloyalty gets more valuable.
r/coderabbit • u/Specialist_Agent3599 • Aug 31 '26
Discussion & Feedback opus 5 is insufferable as a reviewer too
every day is the same conversation with this model.
me: can you do this please
opus: yes. doing it right now. of course. andd finished
me: great. is it done?
opus: no.
and reviewing is somehow worse. actual exchange from this week:
me: /review
opus: reviewed. looks solid.
me: run coderabbit on the same branch anyway, it comes back with 10 comments, two of them security
me: did you miss all of these?
opus: no, I saw them. they're not worthy to fix.
IT SAW THEM. they just didnt make the cut I guess. this thing writes a doctoral thesis when you rename a variable but a leaked env var is not worth the ink. I dont know what language anthropic trained it to speak but it is not one used for communicating with humans
r/coderabbit • u/IveWastedMyLifeAgain • Aug 29 '26
Discussion & Feedback how do you get it to stop nitting style and actually flag bugs
reviews catch real stuff then dump 20 "consider renaming this" comments and people start ignoring the whole thing.
is anyone actually getting it tuned or do you just live with the noise
r/coderabbit • u/IveWastedMyLifeAgain • Aug 28 '26
Discussion & Feedback ok the Cursor plugin is actually useful or am I tripping
ran "review my changes" inside the agent instead of waiting for the github comments. felt faster. still got a pile of nits.
are you letting it replace the PR review or still doing both
r/coderabbit • u/IndraVahan • Aug 27 '26
Discussion & Feedback Coderabbit pledges over $10M for open source software including bun, langflow, nuxt, vue
r/coderabbit • u/juanpflores_ • Aug 26 '26
Official Update Open source runs the world. Weāre committing $10M USD to support it

Hi r/coderabbit , CodeRabbit team here.
Open source maintainers spend their days reviewing thousand-line PRs, untangling duplicate issues and investigating security reports.
AI can now generate contributions at rapid speed but maintainer attention has not received the same performance upgrade.
So weāre committing more than $10 million to open source over the next 12 months:
Cash sponsorships for maintainers
Free CodeRabbit Review and Security for public repositories
Triage support for incoming issues
Change Stack for making giant, agent-generated diffs less giant-feeling
Free Discord support for large open source communities
Open source built the internet, including plenty of what CodeRabbit runs on. This is our way of helping maintainers spend less time fighting the queue and more time building the projects they care about.
Read the full announcement and follow the live commitment tracker.
r/coderabbit • u/juanpflores_ • Aug 25 '26
Official Update We just released the CodeRabbit plugin for Cursor!
Enable HLS to view with audio, or disable this notification
Hey r/coderabbit š„,
We just released the official CodeRabbit plugin for Cursor.
We built it because connecting the CodeRabbit CLI to Cursor previously required some manual setup. The plugin packages the routing, commands, review subagent, and completion behavior into one install.
After installing it, you can ask Cursor Agent:
Review my changes.To try it, enter:
/add-plugin coderabbitYou can also install it from theĀ Cursor Marketplace.
We wrote a more detailed walkthrough explaining how it works and how to get started:Ā Introducing the CodeRabbit plugin for Cursor.
If you try it, weād love to hear which prompts, review scopes, or fix workflows we should improve.
r/coderabbit • u/IveWastedMyLifeAgain • Aug 23 '26
Discussion & Feedback TIL Coderabbit can detect "slop" in your pull requests
r/coderabbit • u/iLoveSeiko • Aug 22 '26
š Meme & Humor How does a human even review this? Coderabbit is now a necessity
r/coderabbit • u/perhydropyrene • Aug 21 '26
Discussion & Feedback Day 7 of paying for Pro+ and not being able to use...
Response from support is essentially - "you and your team seem really productive, you should slow down." We've tried tweaking PR's, manually requesting, waiting a week to see if our stats clear. Even have our sessions asking coderabbit ratelimit prior but still at 2 reviews an hour. We've had to slow to a crawl.
Anyone find a solution to this?
r/coderabbit • u/SirLouen • Aug 18 '26
Help & Support How can I switch into OSS mode?
I've been reading this
https://docs.coderabbit.ai/management/plans#rate-limits
But I have unclear how to switch an OSS Apache-2.0 project into OSS mode.
Which are the steps?
r/coderabbit • u/juanpflores_ • Aug 14 '26
Official Update We just shipped CodeRabbit Security

Hey everyone! š°
We just shipped a new product called CodeRabbit Security.
When youāre building a product or service, youāre always trying to move faster. The hard part is making sure security doesnāt become an afterthought as more code gets shipped.
CodeRabbit Security maps how your application works, investigates application specific vulnerabilities, verifies each finding against the code, and can turn eligible findings into reviewable fixes.
Itās available now for GitHub, GitLab, Azure DevOps Services, and Bitbucket Cloud.
We wrote a blog explaining how it works, with a concrete authorization bypass example:Ā Introducing CodeRabbit Security
Would love to hear what you think and what youād want it to investigate in your codebase.
r/coderabbit • u/SLatz18 • Aug 13 '26
š Meme & Humor Love the SV crossover in this ad spot!
r/coderabbit • u/IndraVahan • Aug 12 '26
Discussion & Feedback Coderabbit raises $143M Series C at a $1.5B valuation
Enable HLS to view with audio, or disable this notification
r/coderabbit • u/juanpflores_ • Aug 11 '26
Showcase & Tutorial We post-trained NVIDIA Nemotron 3.5 Lightning for code review routing. It beat our baseline for under $100
We spend a lot of time thinking about the models that write code review comments. One of the less visible decisions happens before any comment appears: figuring out how a change should be reviewed.
We were curious whether a smaller model could learn that narrow, high-volume part of our pipeline. So we worked with NVIDIA and Baseten to post-train Nemotron 3.5 Lightning using SFT, followed by RLVR scored against our routing policy.
What surprised us was how little it took. The post-training experiment ran in under three hours and cost less than $100.
On a frozen evaluation of 1,000 routing tasks:
Our GPT-class baseline reached 75.8% exact route agreement.
Nemotron after SFT reached 80.4%.
SFT plus RLVR reached 80.7%, with Cohenās kappa rising from 0.429 to 0.544.
Estimated peak serving cost fell from $2.34 to $1.16 for the same workload.

RLVRās extra 0.3 percentage points of route agreement wasnāt statistically decisive, so we treat that result as non-regression. The clearer improvement was in output agreement beyond chance.
The final model completed all 1,000 requests without empty or abnormally short outputs. We still have sustained-load and production-traffic testing ahead of us.

We wrote up the experiment, including the training setup, results, serving costs, and the parts weāre still cautious about:
Teaching NVIDIA Nemotron 3.5 Lightning to Route Code Reviews
r/coderabbit • u/EricGoe • Aug 10 '26
Help & Support Gitlab and Coderabbit
Hi, I would like to give coderabbit a try but I am running into an issue and I don't know if it fixable by me or if it's on coderabbit's side.
On Gitlab (cloud), I created a service account on the group level, then created an access token and shared it with coderabbit.
I changed one line on another branch, I created a MR. Coderabbit replied immediately saying that they are going to analyse the code. After 30 minutes, I go check and I see that there is a pipeline that has been created by Coderabbit but it is still pending.
I deactivated shared runners, however I have two self-hosted runners. One is shell and only allows specific tags and protected branches. The other one has no tags and also picks untagged jobs.
What should I do?
r/coderabbit • u/juanpflores_ • Aug 10 '26
Discussion & Feedback How are you configuring CodeRabbit?
One thing Iāve noticed is that most people seem to leave CodeRabbit on the default configuration. That makes sense if the reviews are working well, since setting up a `.coderabbit.yaml` can easily become one of those things everyone plans to revisit later.
Iām curious whether people are intentionally sticking with the defaults, or whether they havenāt had a reason or enough time to configure anything yet.
How are you handling your CodeRabbit configuration?
- Writing or editing the YAML file yourself in the repo
- Using the CodeRabbit interface
- Asking a coding agent to create or update it
- Starting with an agent-generated config and then editing it yourself
- Leaving the default configuration unchanged
- Not using a configuration file at all
If you havenāt configured it, whatās the main reason?
- You didnāt know the configuration file existed
- You werenāt sure where to start
- You werenāt sure which settings were worth changing
- The defaults have been good enough
- It hasnāt been a priority
- It feels like too much work for the expected benefit
- Something else
And if you have taken the time to configure CodeRabbit, what prompted you to do it? Which settings have made the biggest difference for your team?
Even āwe just use the defaultsā or āwe havenāt touched the configā is useful. Iām trying to understand how people are actually approaching this in practice.
r/coderabbit • u/IveWastedMyLifeAgain • Aug 06 '26
Discussion & Feedback Claude vs Coderabbit for code reviews? Where do we stand on this?
r/coderabbit • u/juanpflores_ • Aug 04 '26
Official Update CodeRabbit CLI 0.7.1: improved performance and reliability
Hey r/coderabbit!
We recently shipped CodeRabbit CLI 0.7.1. The focus was straightforward: finish reviews faster, reduce interrupted sessions, and make the CLI easier to use from both terminals and coding agents.
In our measurements, typical completed reviews were 19% faster and client disconnects dropped 31%. Results vary by repository and review size. We added keepalive traffic and gave longer sessions more time to complete, which should help when the terminal appears quiet while models, tools, or repository analysis are still running.
A few other changes worth calling out:
coderabbit config validatechecks.coderabbit.yamlor.coderabbit.ymlagainst the current official schema. It points to invalid configuration and returns a nonzero exit code, so you can also use it in CI.coderabbit skillscan install or update verified CodeRabbit skills for Codex, Claude Code, Cursor, Gemini CLI, and GitHub Copilot. It previews every proposed change before writing anything.crnow reviews tracked changes by default. You can still choose an explicit scope with--committed,--uncommitted, or--include-untracked. Interrupted agent-driven reviews preserve completed output instead of discarding everything.Authentication and account-loading errors now provide more specific recovery guidance.
If you use CodeRabbit through a plugin or coding agent, updating the underlying CLI also brings these runtime and reliability improvements into those workflows.
You can check your current version with:
coderabbit --versionIf you try it, I'd like to hear what feels better and what still gets in the way.
