Skip to main content
A pull request review arrives after the code is pushed. By then a reviewer is waiting, and every fix is another commit and another round of review. CodeRabbit’s local reviews move that check to before the push. They review the committed and uncommitted changes in your working copy and report findings where you work: in your terminal or in your editor. You don’t need a pull request, and you can hand the findings to a coding agent to fix. There are three ways to run a local review. Pick the one that matches where you write code.

CLI

For the terminal, scripts, and coding agents. Run a review yourself, or have an agent such as Claude Code, Cursor, Codex, or Gemini run it and act on the findings.

VS Code extension

For VS Code and editors built on it, such as Cursor and Windsurf. Findings appear in the CodeRabbit sidebar and as comments in the editor, and Fix with AI hands them to your coding agent.

JetBrains plugin

For IntelliJ IDEA, PyCharm, WebStorm, and other IntelliJ-based IDEs except Rider. Findings appear in a native tool window, and a suggestion applies as one edit you can undo.

Which one to use

The VS Code extension and the CLI are independent, and you can use both side by side.

How local reviews differ from Pull Request Reviews

What’s next

Get started with the CLI

Install the CLI, authenticate, and review your local changes.

Install the VS Code extension

Install CodeRabbit in VS Code, Cursor, Windsurf, or another VS Code-based editor.

Install the JetBrains plugin

Install the plugin from the JetBrains Marketplace beta channel and sign in.