> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# CodeRabbit for JetBrains IDEs

> Review local Git changes with CodeRabbit in IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs before you open a pull request, from a native tool window that also works in JetBrains Remote Development.

Cloud Only (This feature is available on CodeRabbit Cloud only. It is not available on self-hosted CodeRabbit deployments.)

Open Beta (The CodeRabbit plugin for JetBrains IDEs is in beta.)

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](https://docs.coderabbit.ai/ide/jetbrains/privacy.md#what-a-review-sends). The plugin also works in [JetBrains Remote Development](https://docs.coderabbit.ai/ide/jetbrains/install.md#use-jetbrains-remote-development).

Using VS Code, Cursor, or another VS Code-based editor? See the [IDE extension](https://docs.coderabbit.ai/ide.md) instead.

## What you can do

* [Choose what to review](https://docs.coderabbit.ai/ide/jetbrains/review.md#choose-what-to-review): all changes, committed changes, or selected uncommitted files, compared against a base branch you pick.
* [Review after each commit](https://docs.coderabbit.ai/ide/jetbrains/review.md#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](https://docs.coderabbit.ai/ide/jetbrains/findings.md#go-to-a-finding-in-the-editor), compare the reviewed and suggested code, and [apply a suggestion](https://docs.coderabbit.ai/ide/jetbrains/findings.md#apply-a-suggestion) as one edit you can undo.
* [Hand findings to a coding agent](https://docs.coderabbit.ai/ide/jetbrains/findings.md#fix-with-ai): Claude Code, Codex CLI, or opencode in the IDE terminal, or copy the prompt to use anywhere.
* [Revisit earlier reviews](https://docs.coderabbit.ai/ide/jetbrains/findings.md#review-history) 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](https://docs.coderabbit.ai/cli.md).

For everything the plugin needs, see [Requirements](https://docs.coderabbit.ai/ide/jetbrains/install.md#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](https://docs.coderabbit.ai/management/plans.md#rate-limits) for each plan's numbers.

On a paid plan, you also need a CodeRabbit seat in the organization; see [Seat assignment](https://docs.coderabbit.ai/management/seat-assignment.md). 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](https://docs.coderabbit.ai/ide/jetbrains/review.md#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](https://docs.coderabbit.ai/cli.md), 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](https://docs.coderabbit.ai/ide.md#how-ide-reviews-compare-with-pull-request-reviews-and-the-cli). 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](https://docs.coderabbit.ai/ide/jetbrains/review.md#which-review-configuration-applies), 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](https://docs.coderabbit.ai/ide/jetbrains/troubleshooting.md#known-limitations-in-the-beta) before you report a problem, and send problems and ideas through [support](https://docs.coderabbit.ai/support). To tell CodeRabbit that a single finding was wrong, use [Feedback](https://docs.coderabbit.ai/ide/jetbrains/findings.md#give-feedback-on-a-finding) on the finding.

## What's next

> [card] [Install and set up](https://docs.coderabbit.ai/ide/jetbrains/install.md)
>
> Install the plugin from the beta channel, sign in through your browser, and choose your organization and region.

> [card] [Run a review](https://docs.coderabbit.ai/ide/jetbrains/review.md)
>
> Pick the changes and base branch to review, then start a review from the tool window or after each commit.

> [card] [Findings and Fix with AI](https://docs.coderabbit.ai/ide/jetbrains/findings.md)
>
> Jump to findings in the editor, apply suggestions, and send fixes to Claude Code, Codex CLI, or opencode.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.