> ## 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. # Troubleshoot the JetBrains plugin > Fix common problems with the CodeRabbit plugin for JetBrains IDEs: installing from the beta channel, sign-in that doesn't return to the IDE, connection errors, reviews that don't start, are skipped, or fail, findings that won't open or apply, and Fix with AI agents that don't start. Open Beta (The CodeRabbit plugin for JetBrains IDEs is in beta.) 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](https://docs.coderabbit.ai/ide/jetbrains/install.md#requirements). * Check the plugin version in **Settings → Plugins**, on the **Installed** tab. During the beta, a newer version may fix your problem; see [Update](https://docs.coderabbit.ai/ide/jetbrains/install.md#update-roll-back-or-uninstall). * The plugin writes little to the IDE log, so the tool window's message is usually the best clue. If you contact [support](https://docs.coderabbit.ai/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](https://docs.coderabbit.ai/ide/jetbrains/install.md#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](https://docs.coderabbit.ai/ide/jetbrains/install.md#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: | Message | What to check | | - | - | | "CodeRabbit could not reach the service. Check your network, VPN, and deployment URL in CodeRabbit settings, then retry." | Your network connection and VPN | | "CodeRabbit could not resolve the service address. …" | DNS, and the **Deployment** setting | | "The CodeRabbit connection timed out. …" | Your network connection and VPN | | "CodeRabbit could not establish a secure connection. …" | A proxy or security product that replaces certificates; ask your administrator to trust it in the IDE | Make sure your network allows the [hosts the plugin uses](https://docs.coderabbit.ai/ide/jetbrains/privacy.md#network-access), 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](https://docs.coderabbit.ai/ide/jetbrains/install.md#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"](#intellij-could-not-save-your-coderabbit-sign-in). * Git is on the host's `PATH`. ## Before a review starts | Message | Cause | Fix | | - | - | - | | "Set a base branch in Review options." | The plugin found none of `origin/main`, `origin/master`, `main`, or `master`. | [Set the base branch](https://docs.coderabbit.ai/ide/jetbrains/review.md#pick-the-base-branch) in **Review options**. | | "fatal: not a git repository …" | The project's root folder isn't in a Git repository. | Open the repository's root folder as the project. | | "Git could not be started." | Git isn't installed or isn't on the `PATH` of the IDE. | Install Git, add it to the `PATH`, and restart the IDE. In Remote Development, Git must be on the host. | | "Git did not respond while preparing the review." or "Git produced too much data for an IDE review." | The changes are too large for Git to prepare in time. | Review fewer changes: use a **Scope directory**, or the **Review all uncommitted files** scope with fewer files selected. | | "The selected changes exceed the 20 MB IDE review limit. Select fewer files." | The review is too large; see [What gets reviewed](https://docs.coderabbit.ai/ide/jetbrains/review.md#what-gets-reviewed). | Select fewer files, or set a **Scope directory**. | | "The selected base revision is not valid." | **Base commit** doesn't name a commit, or a review after the first commit in a repository has no parent to compare with. | Fix or clear **Base commit**. | | "No changed files to review" on the button | Nothing in the scope differs from the base. | Check the scope and the base branch, then refresh the file list. | | The button is disabled, with "Refresh changes to review the current scope." | You changed **Review options** after the file list loaded. | Select the refresh button in **Files to review**. | | "A CodeRabbit review is already running." | Each project runs one review at a time. | Wait for it, or select **Cancel review**. | ## 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](https://docs.coderabbit.ai/management/seat-assignment.md). 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](https://docs.coderabbit.ai/configuration/path-instructions.md#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](https://docs.coderabbit.ai/ide/jetbrains/review.md#limits-and-seats). If it keeps happening when you haven't run many reviews, contact [support](https://docs.coderabbit.ai/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](#connection-errors), 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](https://docs.coderabbit.ai/ide/jetbrains/findings.md#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](https://docs.coderabbit.ai/ide/jetbrains/install.md#install-from-the-beta-channel). ## What's next > [card] [Install and set up](https://docs.coderabbit.ai/ide/jetbrains/install.md) > > Check the requirements, install from the beta channel, and sign in again. > [card] [Run a review](https://docs.coderabbit.ai/ide/jetbrains/review.md) > > See how scopes, the base branch, and limits work. > [card] [Get support](https://docs.coderabbit.ai/support) > > Contact CodeRabbit about a problem these pages don't solve. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.