Konrad Sopala
May 27, 2026
5 min read
May 27, 2026
5 min read
Share
Cut code review time & bugs by 50%
Most installed AI app on GitHub and GitLab
Free 14-day trial
CodeRabbit Review went live earlier this month. It’s a new review interface that takes a pull request and reorganizes it from a flat file list into ordered cohorts and layers, so you can read the change in the order it was actually built. In the two weeks since its release, a handful of features have landed on top of it. Here's a look at what's new:
A modern pull request is rarely one thing, especially when an AI agent wrote it. A single PR can now touch a new data model, the backend that consumes it, an unrelated bug fix, and a config change - all in the same diff. Reading top to bottom means context-switching between unrelated topics every few files.
Change Stack groups the diff into cohorts: small, independent units of related work. Each cohort is its own mini walkthrough, with its own ordered layers, range-specific summaries, and diagrams where they earn a place. You can finish one cohort and pick up the next without having to hold the whole PR in your head at once.
For a handwritten 80-line change, this feature may not matter much. But for a 1,400-line AI-authored PR that touches three unrelated concerns, it's the difference between "I'll review this tomorrow" and actually reviewing it now.
You're reading a diff hitting a function call and you face quite an obvious question. Where is this defined, and what else calls it?
The honest answer for most reviewers is, "I'll open it in another tab and grep around." This usually means a few minutes of orientation, then forgetting where you were in the review.
Code Peek removes that detour. Click any variable, function, class, or type name in the diff, and Change Stack looks up its likely definition and usages inline, using GitHub code search and showing the surrounding context, so you can follow the code without leaving the page. When a result points to a file that's actually changed in the PR, an Open in Change Stack action jumps you directly to that file. CodeRabbit Review also keeps an in-page back trail, so you can chase a symbol three files deep and still get back to where you started.
It's the kind of small thing that makes a long review feel less like an archaeological dig.
Walkthroughs and range summaries answer the questions most reviewers often ask. But sometimes you may have a specific inquiry or request that isn’t covered:
The Chat Agent tab in Change Stack allows you to make those inquiries right where you are working. It has the full context of the PR - every cohort, layer, changed line - and answers in the same view you're already working in. You're not flipping over to a separate chat window to ask the AI to summarize the PR because the AI is already sitting on the same diff you’re in.
It's most useful for the kind of question you'd otherwise ask a teammate who wrote the PR. Except no one has to be online for you to ask it.
A long PR begets a long list of CodeRabbit findings, and not every finding is the same. Some are blocking, some are improvements, some are nits.
Change Stack now surfaces four severity buckets by which you can filter and group:
These are separate from two other label families CodeRabbit already attaches to comments. Comment type tells you what kind of feedback it is: potential issue, refactor suggestion, or nitpick and Effort tells you what the fix is worth: quick win, heavy lift, poor tradeoff or low value. Stack the filters together and you can do things like "show me only critical or major potential issues", which is useful when you're deciding whether a PR is shippable in the next hour or genuinely needs a second pass.
If you've been opening large AI-generated PRs and bouncing between files trying to reconstruct what depends on what, Cohorts and Code Peek should take a chunk of that work off your plate.
If you've ever wanted to ask a PR a question instead of re-reading the whole thing to find the answer, now you can with the Chat Agent.
And if your CodeRabbit findings list has been quite long, the severity filters should help you cut through it faster.
Change Stack is in early access and currently only available in GitHub. It's available to all users during the launch window and will be part of the Pro+ plan going forward. Click the Review Change Stack button in your next CodeRabbit PR comment to try it.
