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 you get. A local review reports findings. A Pull Request Review adds the rest: the summary, the PR Walkthrough, and chat on the pull request.
- Which configuration applies. The VS Code extension uses your organizationâs settings plus the
.coderabbit.yamlin your workspace folder; see which review configuration applies. The CLI has its own configuration discovery. - Limits. The VS Code extension, the CLI, and Pull Request Reviews each have their own hourly review limit per developer. See Plans and pricing.
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.