Skip to main content
During the beta, CodeRabbit publishes the plugin on the beta channel of JetBrains Marketplace. This page covers installing it from that channel, signing in, the plugin’s settings, JetBrains Remote Development, and updating or removing the plugin.

​
Requirements

  • A JetBrains IDE built on the IntelliJ platform, version 2025.3 (build 253) or later. Help → About shows the version. CodeRabbit tests IntelliJ IDEA, PyCharm, and WebStorm; see Supported IDEs. Rider isn’t supported.
  • The Git and Terminal plugins that come with the IDE, enabled. CodeRabbit doesn’t load without them.
  • Git installed on the machine where the IDE runs, and on its PATH. The plugin runs git from the PATH; it doesn’t use the Git executable set in the IDE’s version control settings. In Remote Development, Git must be on the remote host.
  • A project whose root folder is a Git repository.
  • A CodeRabbit account on CodeRabbit Cloud, which you sign in to with GitHub, GitLab, Bitbucket, or Azure DevOps, as in the CodeRabbit web app. The plugin doesn’t connect to self-hosted CodeRabbit.

​
Install from the beta channel

CodeRabbit publishes the plugin, ai.coderabbit.jetbrains, on the beta channel of its JetBrains Marketplace page, and JetBrains Marketplace distributes it signed. A search on the IDE’s Marketplace tab doesn’t list beta-channel plugins until you add the channel as a plugin repository. Add it once, and the IDE also offers beta updates.
1

Open the Plugins settings

Open Settings (Ctrl+Alt+S on Windows and Linux, Cmd+, on macOS) and select Plugins.
2

Add the CodeRabbit beta repository

Select the gear icon at the top of the page, then Manage Plugin Repositories. Add this URL and select OK:
3

Install CodeRabbit

On the Marketplace tab, search for “CodeRabbit”. Check that the vendor is CodeRabbit and the plugin ID is ai.coderabbit.jetbrains, then select Install.
4

Restart the IDE if prompted

After the restart, the CodeRabbit tool window appears in the bottom group of the tool window bar.
5

Sign in

Continue with Sign in.

​
Install from a ZIP file

If your IDE can’t use custom plugin repositories, for example because of company policy, install the plugin from a file:
  1. Download the latest beta version from the plugin’s JetBrains Marketplace page, on its Versions tab.
  2. In Settings → Plugins, select the gear icon, then Install Plugin from Disk.
  3. Select the ZIP file itself. Don’t extract it, and don’t select a JAR file from inside it.
  4. Restart the IDE if prompted.
A plugin installed from a ZIP file doesn’t receive updates. To update it, install a newer ZIP file the same way.

​
Sign in

  1. Open the CodeRabbit tool window: select it in the tool window bar, or choose Tools → Review changes with CodeRabbit.
  2. Optionally, select Share usage analytics. It’s off unless you select it; see Usage analytics and error reports.
  3. Select Sign in. The button changes to Waiting for browser…, and your default browser opens the CodeRabbit sign-in page.
  4. Sign in with your Git provider, the same way you sign in to the CodeRabbit web app. If you’re new to CodeRabbit, this creates your account.
  5. If you belong to more than one organization, the browser shows “Choose a CodeRabbit organization”. Pick the organization to use for reviews and select Continue. An organization is the Git provider organization or personal account that CodeRabbit is set up for; with only one, the browser skips this page.
  6. When the browser shows “Sign-in complete. Return to your IDE.”, go back to the IDE. The tool window shows your name, plan, and organization.
The browser hands the sign-in back to the IDE through a local address on 127.0.0.1, so there’s no code or token to copy. The IDE waits 5 minutes for the browser. To stop waiting, select Cancel sign-in next to the button. If the browser never returns to the IDE, see Troubleshooting. The plugin keeps your sign-in in the IDE’s password storage. Every project you open in that IDE uses the same sign-in and organization. The plugin has its own sign-in: signing in to the VS Code extension or the CLI doesn’t sign you in here, and the reverse is true too.

​
Switch organizations

The organization menu in the tool window’s Account section lists the organizations you can switch to: the ones on the same Git provider as the organization you signed in with. Switching clears the review that the tool window shows. You can’t switch while a review is running. To use an organization on a different Git provider, sign out, sign in again, and pick that organization in the browser.

​
Sign out

Select Sign out (the door icon) in the Account section. This removes the stored sign-in from the IDE. It doesn’t delete your saved reviews; see Remove local data.

​
Choose a region

The Deployment setting chooses which CodeRabbit region the plugin signs in to and sends reviews to:
  • United States, the default.
  • European Union, for enterprise organizations whose CodeRabbit data is hosted in the EU.
Your sign-in belongs to one deployment. After you change Deployment, the tool window asks you to sign in again, and so does changing it back.

​
Settings

Open Settings → Tools → CodeRabbit, or choose Settings from the Options menu (⋮) in the tool window’s title bar. The settings apply to every project in the IDE; there are no per-project settings. The review scope and base branch are chosen in the tool window instead; see Choose what to review. The plugin has no default keyboard shortcuts. To add one, assign a shortcut to the Review changes with CodeRabbit action in Settings → Keymap. The action opens the tool window; it doesn’t start a review.

​
Use JetBrains Remote Development

In Remote Development, the plugin runs in two parts: Install the plugin on both sides:
  1. In JetBrains Client, open Settings. Plugins for the remote IDE are under Plugins (Host), and plugins for JetBrains Client under Plugins (Client).
  2. On each of the two pages, add the beta repository and install CodeRabbit, or install the ZIP file.
  3. Restart when prompted. Keep the same plugin version on both sides.
Git must be on the host’s PATH. Sign-in opens the browser on your computer, and the browser returns a one-time sign-in code to JetBrains Client there. JetBrains Client passes the code to the host over the Remote Development connection, and the host exchanges it with CodeRabbit and stores your sign-in in the host IDE’s password storage. Your computer doesn’t store it. The host needs outbound access to CodeRabbit, through the host IDE’s proxy and certificate settings; see Network access. Fix with AI opens its terminal tab on the host, so a terminal agent must be installed there. Terminal agents and Review after commit aren’t verified in Remote Development during the beta. If they don’t work, use Copy to clipboard and start reviews from the tool window.

​
Roll out to a team

During the beta, everything a developer needs is on this page. For a team rollout:
  • Approve the plugin: the plugin ID is ai.coderabbit.jetbrains and the vendor is CodeRabbit. JetBrains Marketplace distributes it signed, on the beta channel.
  • Control versions: the beta repository gives developers each new beta version through IDE updates. A ZIP file stays on one version until someone installs a newer one.
  • Allow network access: see Network access for the hosts on the developer’s computer and, in Remote Development, on the host.
  • Assign seats: on a paid plan, each developer needs a seat; see Seat assignment. CodeRabbit checks the developer’s organization membership and seat on every review, so removing either stops their reviews.
  • Review data handling: see Data, privacy, and network access, including the error reports that are always sent.

​
Update, roll back, or uninstall

  • Update: with the beta repository added, the IDE offers new beta versions with its other plugin updates in Settings → Plugins. A ZIP install doesn’t update; install a newer ZIP file.
  • Roll back: uninstall the plugin, restart the IDE, then install the earlier version from a ZIP file.
  • Uninstall: in Settings → Plugins, on the Installed tab, select CodeRabbit, then Uninstall, and restart the IDE.
Uninstalling leaves your stored sign-in, settings, and saved reviews on your computer. To remove them, sign out and clear your review history before you uninstall; see Remove local data.

​
What’s next

Run a review

Pick the changes and base branch to review, then start a review from the tool window or after each commit.

Privacy and network

See what a review sends, which hosts the plugin connects to, and what it stores on your computer.

Troubleshooting

Fix sign-in, review, and Fix with AI problems, and see the known limitations of the beta.