Troubleshoot the JetBrains plugin

Most problems show a message in the banner at the top of the CodeRabbit tool window. Find the message or symptom below.

​

Start here

• Check that the IDE is version 2025.3 or later and isn’t Rider; see Requirements.
• Check the plugin version in Settings → Plugins, on the Installed tab. During the beta, a newer version may fix your problem; see Update.
• The plugin writes little to the IDE log, so the tool window’s message is usually the best clue. If you contact support, include the message, the IDE and plugin versions, and the file from Help → Collect Logs and Diagnostic Data.

​

Install and sign-in

​

CodeRabbit doesn’t appear in the Marketplace search

During the beta, the plugin is on the JetBrains Marketplace beta channel, and the IDE’s Marketplace tab lists it only after you add that channel as a plugin repository. See Install from the beta channel. If it still doesn’t appear, the IDE is older than version 2025.3 or is Rider, which the plugin doesn’t support.

​

Sign-in doesn’t return to the IDE

After you sign in, the browser sends the result to the IDE at http://127.0.0.1 on your computer. If that doesn’t happen within 5 minutes, the tool window shows “Sign-in timed out. Try again or select Trouble signing in? for browser recovery steps.”

• Make sure the browser runs on the same computer as the IDE, or, in Remote Development, as JetBrains Client.
• Make sure no browser extension, security software, or company policy blocks http://127.0.0.1.
• Select Trouble signing in? in the tool window and follow its steps: sign out of CodeRabbit in the browser, clear the CodeRabbit site’s local and session storage in the browser’s developer tools (Application tab), then cancel the pending sign-in and start again. Clear storage for the CodeRabbit site only.

​

”IntelliJ could not save your CodeRabbit sign-in”

The IDE couldn’t save your sign-in in its password storage. The message names IntelliJ in every JetBrains IDE. Check the storage in Settings → Appearance & Behavior → System Settings → Passwords. On Linux, the system keychain option needs a running keyring service; choosing In KeePass works without one. This often matters on a headless Remote Development host, where the sign-in is stored. Then sign in again.

​

”This CodeRabbit session belongs to another deployment. Sign in again.”

You changed Deployment in the settings after you signed in. Your sign-in belongs to one region, so sign in again. See Choose a region.

​

”Your CodeRabbit session expired” or “CodeRabbit could not refresh the session”

Sign in again. If this happens while you’re first signing in, CodeRabbit couldn’t complete the sign-in: check your network, then try again.

​

The organization you need isn’t in the menu

The organization menu lists only organizations on the same Git provider as the one you signed in with. To switch to an organization on another provider, sign out, sign in again, and pick it in the browser.

​

Connection errors

When the plugin can’t reach CodeRabbit, the tool window shows the sign-in screen with one of these messages, even though your sign-in is still stored: Make sure your network allows the hosts the plugin uses, including WebSocket (WSS) connections to ide.coderabbit.ai, or ide.eu.coderabbit.ai when Deployment is European Union. Then choose Refresh from the tool window’s Options menu (⋮) to try again without signing in.

​

Remote Development checklist

If sign-in or reviews hang only in Remote Development, check that:

• The plugin is installed on both the host and JetBrains Client, in the same version; see Use JetBrains Remote Development.
• The host can reach app.coderabbit.ai and ide.coderabbit.ai on port 443 (app.eu.coderabbit.ai and ide.eu.coderabbit.ai for the European Union deployment), through the proxy and certificates set in the host IDE.
• The host IDE can store passwords; see “IntelliJ could not save your CodeRabbit sign-in”.
• Git is on the host’s PATH.

​

Before a review starts

​

Review skipped or failed

​

Review skipped because you have no seat

The tool window shows Review skipped with a message that says no CodeRabbit seat is assigned to your account, or that all of the organization’s seats are assigned. Ask an organization administrator to assign you a seat. If you’re the administrator yourself, for example of your personal account’s subscription, assign the seat in the CodeRabbit web app; see Seat assignment. The plugin doesn’t offer a free review without a seat.

​

Review skipped with “Too many files!”

The review has more files than CodeRabbit accepts. The message suggests CLI commands; in the plugin, narrow the review instead: set a Scope directory, set a closer Base commit, or use the Review all uncommitted files scope with fewer files selected.

​

Review skipped with “There were no reviewable changes in the selected files”

None of the files in the review had changes CodeRabbit could review, for example because path filters exclude them or they were all sent without content.

​

”The CodeRabbit review ended without a completion event”

CodeRabbit stopped the review on its side. Most often, you reached your hourly IDE review limit; during the beta, the plugin shows this message instead of the wait time. Wait, then select Review again. See Limits and seats. If it keeps happening when you haven’t run many reviews, contact support.

​

”Your Git provider access needs reauthorization”

Sign out, sign in again, and authorize CodeRabbit for your organization in the browser.

​

”You are not a member of the requested organization.”

Pick an organization you belong to in the organization menu, or sign out and sign in again.

​

Review failed

“CodeRabbit could not finish this review. Check your connection and try again.” means the connection dropped or CodeRabbit couldn’t complete the review. Check the connection, then select Review again.

​

Findings and Fix with AI

​

A finding doesn’t open in the editor or has no marker

• Selecting a finding in the list only shows its details. Select the location link in Finding details, or choose More actions → Open in editor.
• “The finding file is not available in this project.” usually means the repository is in a folder inside the project. Open the repository’s root folder as the project.
• “The finding range is no longer present in this file.” means the file got shorter since the review. Run the review again.
• Editor markers appear only for open findings of the review that the tool window shows.

​

A suggestion won’t apply

The plugin applies a suggestion only if the reviewed lines are unchanged. See Apply a suggestion for each message and what to do.

​

The coding agent doesn’t start

• “command not found” in the terminal: install the agent’s command-line tool (claude, codex, or opencode), make sure it’s on the PATH of the shell set in Settings → Tools → Terminal, and restart the IDE.
• “The shell did not become ready”: the terminal took more than 30 seconds to start. The prompt is on your clipboard; paste it into the agent once the shell is ready.
• Windows: the plugin starts the agent with Command Prompt syntax. If your terminal uses PowerShell and the agent doesn’t start, set the shell to cmd.exe in Settings → Tools → Terminal, or use Copy to clipboard.
• Remote Development: terminal agents aren’t verified there during the beta. Use Copy to clipboard.

In every case, the prompt is already on your clipboard, so you can paste it into the agent yourself.

​

Known limitations in the beta

• Rider isn’t supported. IDEs other than IntelliJ IDEA, PyCharm, and WebStorm can install the plugin but aren’t tested.
• Self-hosted CodeRabbit isn’t supported.
• Without a seat, the review is skipped; there’s no free review. At the hourly limit, the plugin shows neither the wait time nor Review with credits.
• The plugin doesn’t notify you when a review finishes.
• Reviews read files from disk, so unsaved changes aren’t reviewed, and the plugin never fetches the base branch.
• If the repository is in a folder inside the project, findings can’t open in the editor.
• Review after commit reviews only the last commit, and only for commits made with the IDE’s commit tool.
• Ignoring or applying a finding is saved only on your computer.
• In Remote Development, Review after commit and terminal agents for Fix with AI aren’t verified.
• Proxies that require authentication may not work.
• CodeRabbit Plan isn’t available in the plugin.

​

Reset the plugin

To start over:

1. Choose Clear local review history… from the tool window’s Options menu (⋮).
2. Select Sign out.
3. Uninstall the plugin, restart the IDE, and install it again.

​

What’s next