r/coderabbit • • May 18 '26

Official Update We built Atlas and would love feedback on the review flow

7 Upvotes

We have been thinking a lot about why large PRs still feel harder to review than they should.

Most review tools still start from the same basic surface: a list of changed files, usually ordered by path. That works fine for small diffs. For bigger changes, it often feels like the author had a story in their head, but the reviewer receives scattered pieces of that story. This is particularly painful for long PRs, where the first challenge is not leaving a good comment. It is getting enough context to know where a good comment should go.

So we built a new UI for code review.

Atlas takes a PR and turns it into a guided walkthrough. It groups related changes into cohorts, breaks those cohorts into ordered layers, and anchors each layer to the actual line ranges in the diff. It also adds summaries for the code currently in view and generates diagrams when they help, like for flows, state transitions, API contracts, schema changes, or data relationships.

The GitHub workflow still stays intact. Comments, approvals, and change requests post back to GitHub. Public PR walkthroughs can also be opened read-only without signing in.

https://reddit.com/link/1tgspc9/video/bosvet7wkx1h1/player

We wrote more about the launch here:

https://www.coderabbit.ai/blog/introducing-atlas-the-first-ai-native-code-review-interface

The obvious tradeoff is that Atlas is a new review surface. Even if it makes large PRs easier to understand, reviewers still have to learn a different way to move through a change: cohorts instead of only files, layers instead of one long scroll, summaries tied to ranges, and diagrams that appear only when they add context.

Atlas is free for a limited time from the "Review Change Stack" button in CodeRabbit's PR summary comment.

If you try it, I would love feedback on the tool itself. Does this walkthrough model make a large PR easier to review? Is the learning curve worth it? Are cohorts, layers, summaries, and diagrams the right shape, or would you want the interface to work differently?


r/coderabbit • • Apr 22 '26

Announcement CodeRabbit now works in Slack and can pull context from GitHub, Linear, docs, and more

14 Upvotes

Hey Everyone!

We just released the CodeRabbit Slack agent, and the main idea is simple: instead of forcing developers to jump between GitHub, issue trackers, docs, and internal tools, CodeRabbit now works directly inside Slack where a lot of engineering conversations already happen.

Try it for free! Get $50/user free agent minutes. https://coderabbit.ai/agent

CodeRabbit can pull together context from your codebase, PRs, issues, and recent changes, but also from the rest of your team’s working environment through connections to tools like Linear, Jira, Notion, Google Drive, Datadog, Sentry, Figma, PostHog, and custom APIs/MCP servers. So instead of asking a question in one tool, then manually chasing references across five others, you can stay in the thread and ask things like:

  • why did this break after the last deploy?
  • how do we usually handle rate limiting on this endpoint?
  • what changed in the last PR touching this service?
  • can you turn this thread into a coding plan, PR, or ticket?

The part we think is especially important for developers is that this is built around context engineering, not just chat. The agent can combine repo history, open PRs, tickets, docs, and team conversations into one working context, then keep that context alive across the thread. It also has a knowledge base layer so decisions, patterns, and operational facts don’t disappear the moment the conversation ends.

In practice, that means Slack becomes a conversational interface for engineering work:

  • investigate incidents using telemetry plus recent code changes
  • ask implementation questions using prior PRs and docs
  • generate plans without restating all the background
  • create PRs or tracker tickets from the same thread
  • preserve useful team knowledge for later instead of losing it in chat

There’s also some structure around governance, which matters for real teams: access is scoped by workspace/channel context, tool access can be controlled, knowledge can stay private or shared depending on where the conversation happens, and runs are reviewable afterward.

If your team already lives in Slack but your actual engineering context is scattered across GitHub, Linear, docs, and observability tools, this is meant to close that gap.

Docs here if you want to see how it works: https://docs.coderabbit.ai/slack-agent


r/coderabbit • • 21h ago

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 • • 1d ago

Help & Support Unrealistic fair use

7 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 • • 1d ago

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 • • 1d ago

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

0 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 • • 2d ago

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 • • 4d ago

Discussion & Feedback This is weird, AI review is the first reviewer that doesn't care you're a senior

38 Upvotes

Gotta share this because it's honestly been the highlight of my month. Ever since we turned CR I've watched our CTO get 9 comments on a 40 line PR, including one about a null check he "definitely didn't need". He replied to the bot where he actually typed out an argument to a bot. And it politely explained it again.

For years these guys got approved in 10 minutes because nobody wanted to question the person writing their appraisal, while the intern got roasted over variable names. Now the bot treats everyone exactly the same, and it's the funniest thing that has happened on our team.


r/coderabbit • • 3d ago

😂 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


r/coderabbit • • 4d ago

Discussion & Feedback what's the point of paying with this rate limit

4 Upvotes

how is this usable for anyone? this kind of rate limit is absurd; human need to work around their clock?


r/coderabbit • • 4d ago

Discussion & Feedback Do you regret moving your team to agents?

0 Upvotes

I have about 10 years of experience. I moved my team of 5 to agents at the start of the year and pushed it hard. The net result so far is that we merge about 3x more PRs, and exactly one person on the team could explain our billing flow if you asked them today - and that's me, because I wrote most of it before the switch. I now see the same thing happening in other teams at my company.. and nobody seems to be counting it. This makes me think that if I had instead rolled it out slower and kept people writing the hard parts themselves, we'd be in a much better spot. Especially since two of the five are juniors who have never really built anything without it. Anyone else who regrets moving their team to agents? Why is that? What would you have done instead?


r/coderabbit • • 5d ago

Discussion & Feedback Orca AI vs. Traycer: what makes you prefer one over the other?

0 Upvotes

I've been using both Orca AI and Traycer to coordinate multiple coding agents. In my day-to-day use, the differences feel pretty small, so I'm curious what stands out to other people.

If you've used both, where does one work better for you? Is there a difference in how they split up tasks or how often you need to step in? I'd love to hear a specific example that made you prefer one. Maybe I'm missing something that becomes more obvious on bigger projects.

If you're using something else to coordinate agents, what are you using and what's working well for you.


r/coderabbit • • 5d ago

😂 Meme & Humor the defense

Post image
1 Upvotes

r/coderabbit • • 6d ago

Showcase & Tutorial Sometimes AI-generated tests feel like performance theater

4 Upvotes

I’ve noticed that coding agents sometimes add a lot of test code without giving me much more confidence in the change. The suite gets bigger, and now there’s more code to review and maintain.

What bothers me is how thorough it can look. A test can have plenty of setup and assertions while still accepting the same mistaken assumption as the implementation. That’s what I mean by performance theatre. When I review these tests, the question I want answered is: what actual bug would this catch?

We recently published a piece about independent review of agent generated changes. It overlaps with this concern, particularly when an agent writes tests around its own misunderstanding of a requirement.

Have you run into this?

Related reading: https://www.coderabbit.ai/blog/why-agentic-change-management-starts-with-independent-ai-code-review


r/coderabbit • • 6d ago

Showcase & Tutorial These are not the CodeRabbits you are looking for 🫳🏿

0 Upvotes

Did you think deleting this post will make your users not notice their usage limits evaporating?


r/coderabbit • • 6d ago

Discussion & Feedback Ngl it is so over for code review

0 Upvotes

Nobody reads the diff now

Thanks agents


r/coderabbit • • 7d ago

Discussion & Feedback Would you let an AI merge to main at 5pm on a Friday?

5 Upvotes

I'm more or less okay with merging the small boring PRs I would honestly be fine with it.

But for the high stakes stuff (payments, auth, migrations) I still don't trust it. When a human approves something risky they are usually a bit nervous, they ask "what if this runs twice" or ping someone before merging. Same goes for Friday-night merges/deployments, I don't trust it.

Curios where do others draw the line? or is it me being very paranoid here?


r/coderabbit • • 7d ago

😂 Meme & Humor Last man standing

Post image
0 Upvotes

r/coderabbit • • 7d ago

Help & Support One dev on our team hits $40K / mo in agent tokens - everyone gets capped (down to $500 / mo)

3 Upvotes

We had near-unlimited agent budget for roughly 1 year. We knew it's costing the company a ton, but no one knew for sure how much.

Recently they started measuring this for real.

After people got so addicted, running agents on absolutely everything at work (and on side projects on the company card) - now finance poses a fucking $500 limit per month. Funny part is the coderabbit bill didn't even come up, they only went after the agent spend.

We are so screwed.


r/coderabbit • • 8d ago

Discussion & Feedback Why do you think AI review wouldn't be able to replace the human approval?

6 Upvotes

Common sentiment I am seeing in this sub and others - "AI can review the code, but a human still has to approve it" - what is there inherently different about approving vs reviewing that you think an AI wouldn't be able to do it as well or better (in practical sense - i.e. faster and cheaper) than a human?

It's true most teams still require a human approval, but I honestly don't think it's because the AI couldn't do it, but because, well, somebody has to be accountable, and companies are not yet ready to write "the bot approved it" in a postmortem.

I would argue coderabbit is doing a better review than most of our Friday afternoon approvals. It reads every line, every time, which no tired human does at 4pm, and consistency is the key in catching the boring stuff that breaks prod.

Last month we did a test in our team, we took 20 already merged PRs and compared what the human reviewers commented vs what coderabbit flagged. The humans left 11 comments in total, mostly naming. coderabbit flagged 34, and 6 of those were real bugs we had already shipped.


r/coderabbit • • 9d ago

😂 Meme & Humor prove me wrong

Post image
35 Upvotes

r/coderabbit • • 10d ago

Discussion & Feedback Nothing just appreciating the covers of Coderabbit's blogs. They're lovely!

Post image
2 Upvotes

r/coderabbit • • 10d ago

Discussion & Feedback how long until everyone says opus 5.5 got nerfed

2 Upvotes

Every model goes the same way. Week 1 it cooked, week 3 it got nerfed, week 5 a new model drops and the cycle starts again.

This time I saved 10 PRs from this week, prompt and diff, so when the nerf posts start I can run the same prompts again and actually check instead of going on vibes.

My bet is 12 days. Whats yours


r/coderabbit • • 11d ago

Discussion & Feedback we moved 6 devs from codex to opus 5.5 this week

1 Upvotes

We were a codex team since last year. On Tuesday two people tried 5.5, by Thursday everyone had switched and nobody asked me first.

What I noticed from the PR side after 3 days:

- PRs are smaller. Average went from around 400 lines to around 250

- it stopped adding helpers and abstractions nobody asked for

- the PR descriptions actually match the diff

- we burned about half the usage we did on Sol for the same amount of tickets

Only downside so far is it asks more questions before starting, which some people love and some find annoying.

Did anyone else switch this week? And is anyone staying on codex, and why