CodeRabbit for JetBrains IDEs

The CodeRabbit plugin reviews your local Git changes in IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs before you open a pull request. It covers the commits on your branch, the edits you haven’t committed yet, or both, so you don’t need to push first. Findings appear in the CodeRabbit tool window and as markers in the editor, where you can apply a suggested fix or hand the finding to a coding agent. Each review sends your changed files to CodeRabbit; see what a review sends. The plugin also works in JetBrains Remote Development. Using VS Code, Cursor, or another VS Code-based editor? See the IDE extension instead.

​

What you can do

• Choose what to review: all changes, committed changes, or selected uncommitted files, compared against a base branch you pick.
• Review after each commit you make in the IDE, automatically or after asking. It’s off until you turn it on.
• Go to a finding in the editor, compare the reviewed and suggested code, and apply a suggestion as one edit you can undo.
• Hand findings to a coding agent: Claude Code, Codex CLI, or opencode in the IDE terminal, or copy the prompt to use anywhere.
• Revisit earlier reviews of the repository.

​

Supported IDEs

The plugin runs in JetBrains IDEs built on the IntelliJ platform, version 2025.3 or later. CodeRabbit tests it in IntelliJ IDEA, PyCharm, and WebStorm. Other IntelliJ-based IDEs, such as GoLand, PhpStorm, RubyMine, CLion, RustRover, DataGrip, and Android Studio, can install it, but they aren’t tested during the beta. Rider isn’t supported. In Rider, run reviews from the terminal with the CLI. For everything the plugin needs, see Requirements.

​

Plans and limits

The plugin works on the Free plan and during a trial. Each review counts toward your plan’s hourly IDE review limit, which the plugin shares with the VS Code extension. That limit is separate from your pull request and CLI review limits. See Rate limits for each plan’s numbers. On a paid plan, you also need a CodeRabbit seat in the organization; see Seat assignment. Unlike the VS Code extension, the plugin doesn’t offer a free review when you have no seat, and it doesn’t offer Review with credits when you reach the limit.

​

Compared with your pull request review

A review in the plugin uses the same CodeRabbit review service and organization settings as your pull request reviews, but it isn’t the full pull request review:

• You get findings, without the summary, walkthrough, or chat.
• Your organization’s settings and the repository’s .coderabbit.yaml apply, except settings that only make sense on a pull request; see Which review configuration applies.
• Ignoring or applying a finding in the IDE doesn’t change your pull request reviews.
• IDE reviews have their own hourly limit, so they don’t use up your pull request reviews.

The plugin is independent of the CLI, and you can use both. For a side-by-side table of IDE reviews, the CLI, and pull request reviews, see the comparison on the IDE extension overview. That table describes the extension’s sidebar and workspace configuration; the plugin uses a tool window and reads its configuration from the Git repository root, but the comparison with the CLI and pull request reviews is the same.

​

Give feedback on the beta

The plugin is in beta, so its behavior and these pages can change between releases. Check Known limitations in the beta before you report a problem, and send problems and ideas through support. To tell CodeRabbit that a single finding was wrong, use Feedback on the finding.

​

What’s next