Skip to main content
Find your symptom below. Each entry gives the cause and the fix. Entries are grouped by when the problem shows up: during install and sign-in, before a review starts, during and after a review, when you use Fix with AI, and with self-hosted CodeRabbit.

​
Start here

Before you look for your symptom:
  1. Update the extension to the latest version. See Update the extension, which also shows how to find the version you have. Many problems go away with an update.
  2. Open View → Output and select CodeRabbit in the list. The extension logs information, warnings, and errors there. There is no setting for more detailed logs.
  3. If you contact support, include the extension version, your editor and its version, your operating system, the exact message you see, and the relevant lines from the CodeRabbit output.

​
Install and sign-in

​
CodeRabbit is missing from the Extensions view

This happens when your editor installs extensions from a different gallery than the one you searched, or when your editor is older than the extension supports.
  • Search the Extensions view for “CodeRabbit” and check that the publisher is CodeRabbit and the extension ID is coderabbit.coderabbit-vscode.
  • If your editor’s gallery doesn’t list it, get it from the Open VSX listing. The VS Code Marketplace listing installs into VS Code only.
  • Check your editor’s version against the requirements.

​
A new version is available, but the Extensions view offers no update

The extension shows “A new version of the extension (X) is available.” This happens when CodeRabbit has published a version that your editor’s gallery doesn’t offer yet, for example in an editor that installs from Open VSX. Wait until the Extensions view offers the update, or install the new version from a VSIX file. See Update the extension.

​
Browser sign-in never returns to the editor

The CodeRabbit sidebar stays on “Logging in”. This happens when your editor doesn’t open the link the browser sends back, or a different editor window catches it. First, select the button named after your editor on the browser’s success page, such as Open Cursor, and allow the link to open if your editor or browser asks. If the editor still doesn’t respond:
  1. On the browser’s success page, select Copy next to the code field.
  2. In the CodeRabbit sidebar, select Paste code from browser and paste the code.
If Paste code from browser isn’t shown, select the X button to cancel, then Sign in with browser to start again. See If sign-in never returns to the editor. For Codespaces in a browser tab, see Install in remote, container, and cloud workspaces.

​
CodeRabbit sign-in timed out before the browser callback arrived

This happens when the browser doesn’t return to the editor within 5 minutes.
  • Select Retry to wait again, and finish sign-in in the browser.
  • If the browser shows the success page but the editor doesn’t respond, use Paste code from browser as described in Browser sign-in never returns to the editor.
A second timeout ends the attempt with “Authentication timed out”. Select Sign in with browser to start again.

​
Sign-in page says something went wrong

This usually means your editor isn’t one that CodeRabbit’s sign-in page can return to. The page also shows “Please restart sign-in from your IDE.” Check Supported editors. In an editor that isn’t listed, browser sign-in can’t complete, and Paste code from browser doesn’t help because the browser never shows a code. Use the CodeRabbit CLI instead, or use a supported editor.

​
No organization found for this account

This happens when your account isn’t part of any CodeRabbit organization yet.
  • “No organization found for this account. Complete onboarding and try again.” (SSO sign-in): finish onboarding at app.coderabbit.ai, then sign in again.
  • “No organization found for this account. Please contact support.”: contact support.

​
This workspace requires SSO

This happens when your organization requires single sign-on and you signed in another way. Sign out with CodeRabbit: Logout, then sign in again and choose your workspace’s SSO in the browser.

​
This organization is hosted in the EU region

This happens when your account is in a different region than the extension’s coderabbit.accountRegion setting. The extension changes the setting for you and signs you out. Sign in again. See Use an EU-hosted account.

​
Signed out unexpectedly

This happens when CodeRabbit can’t refresh your sign-in, or when your Git provider credentials expire.
  • If you see “Your Git provider credentials have expired or were revoked. Sign in again to restore your CodeRabbit plan.”, select Sign in again.
  • Otherwise, select Sign in with browser.

​
Before the review starts

​
Enable Git to get started or Git repository required

This happens when Git is turned off in your editor settings, or the folder you opened has no Git repository.
  • “Enable Git to get started”: select Enable Git and Refresh.
  • “Git repository required”: open the folder that contains your repository, or select Initialize Git to create one.

​
The review button is disabled, or a review ends with No changes to review

The review button is disabled when the selected scope lists no files. “No changes to review” is a notification that appears when a review starts and finds nothing to send. Common reasons:
  • The scope doesn’t match your changes, for example Committed changes when you haven’t committed yet. Change Changes to review.
  • In Uncommitted changes, no files are selected.
  • The changed files are excluded or ignored by Git, so they aren’t listed. See What gets reviewed.
  • The base branch is wrong. See The review compares against the wrong branch.
  • For “No changes to review”: you already reviewed these changes, and the next review covers only what changed since. See Review again after more changes.
  • For “No changes to review”: the listed files are larger than 5 MB or have empty diffs, which the extension drops when the review starts.
To review the whole branch again, clear its earlier reviews in History.

​
The review compares against the wrong branch

This happens when the extension’s default base branch isn’t the one you merge into. Select Compare against and pick the right branch. The list shows local branches only. If the branch exists only on the remote, create a local branch for it without checking it out, for example git branch release origin/release. If the base branch moved on the remote, run git fetch; the extension never fetches. See Pick the base branch.

​
All seats in the organization are assigned

The review doesn’t start, and “All CodeRabbit seats for the ”…” organization are currently assigned. Ask an organization administrator to add or free up a seat, then try again.” appears. This happens when every seat in your organization is in use. Ask an organization administrator to add or free up a seat. See Without a seat.

​
Rate limit exceeded

This happens when you reach your hourly limit of IDE reviews. The message says how long to wait.
  • Wait the time shown, then start the review again.
  • If the extension offers Review with credits, selecting it runs the review right away and bills it to your organization’s usage. During a promotion, the button reads Run review for free. Free reviews without a seat can’t use credits.
See Hourly limits.

​
The organization is still updating

This happens when you start a review while the extension is still matching your repository to an organization. Wait a moment and start the review again. See Choose the organization for reviews.

​
Too many files in the review

The review is skipped with “Too many files! This PR contains N files, which is X over the limit of M.” The message says “PR” and suggests CLI commands because the CLI shares it; in the editor, it applies to your local review. It happens when the review sends more files than your plan allows; see File limits for the numbers and how files are counted.
  • In Uncommitted changes, select fewer files.
  • In All changes or Committed changes, pick a closer base branch, or switch to Uncommitted changes.
  • Add path filters for files you don’t need reviewed.
  • After a review completes, the next one counts only the files changed since then, so reviewing after each smaller step keeps later reviews under the limit. This doesn’t help the first review of a branch. Path filters in the repository’s .coderabbit.yaml also apply to its pull request reviews.

​
All files are ignored

This happens when the path filters and default ignored paths in your CodeRabbit configuration exclude every file in the review. Check the path_filters in your .coderabbit.yaml and organization settings. See What gets reviewed.

​
Unable to start the review because the diff is too large

This happens when the upload is too big to send in one review. Rebase onto your base branch, select fewer files, or split the changes into smaller reviews, then try again.

​
Could not start review as we are unable to connect to the reviewer

This happens when the extension can’t open its connection to CodeRabbit, usually because of a network, firewall, or proxy problem.
  • Check that your network allows WebSocket connections to ide.coderabbit.ai, or ide.eu.coderabbit.ai for EU accounts. See Network access.
  • If your account is in the EU, check that coderabbit.accountRegion is set to eu. See Use an EU-hosted account.
  • Try again later.

​
During and after a review

​
Review is stuck on Setting up

This happens when CodeRabbit accepted the review but hasn’t reported progress yet, for example while it queues the review or clones the repository, or when a proxy holds the connection open without passing data. After 5 minutes, the extension cancels the review and shows “Review setup timed out. Please try again.” A review that stalls on a later step has no timeout.
  1. Select Stop Review, or wait for the timeout. A review that stalls on a later step needs Stop Review.
  2. Open View → Output and select CodeRabbit. If you see “WebSocket connection error”, the extension can’t reach CodeRabbit: check your network as described in “Could not start review as we are unable to connect to the reviewer”.
  3. Without that error, the cause is still open: a proxy that holds the connection open logs nothing. Update the extension and start the review again.
  4. If it still hangs, send the output lines around the review, such as “Review did not progress beyond setup before timeout”, to support.

​
Review failed or Review completed with warnings

This happens when CodeRabbit can’t review some or all of the files. The view shows the reason, and for warnings, “Files reviewed: X/Y”.
  • Read the message under the review status, then start a new review.
  • A failed review can keep the findings it received before it failed.

​
A review shows as cancelled after switching branches

This happens because switching branches cancels a running review for the branch you left. Its results aren’t added to the editor. Switch back and start a new review. Switching back doesn’t resume the cancelled review.

​
A finding has no comment in the editor

This happens when you changed the code so CodeRabbit can’t find the reviewed lines. Open in editor shows “Could not highlight code. File has been modified since the review.” Run a new review to get findings for the current code.

​
Failed to apply changes

This happens when the code changed after the review, so the suggestion no longer fits. The message gives one of these reasons:
  • “The suggestion’s location has changed. Run a new review before applying it.”
  • “The reviewed location is invalid. Run a new review before applying this suggestion.”
  • “The reviewed code has changed. Run a new review before applying this suggestion.”
  • “The editor could not apply the suggestion.”
  • “The suggestion was applied but could not be saved. Save the file before resolving this comment.”
Run a new review, then apply the new suggestion. For the last reason, save the file yourself.

​
Could not unresolve comment

This happens when the code changed after the review, so the extension can’t place the finding again. Run a new review to get findings for the current code.

​
Nitpick comments disappeared after a reload

This is expected. Nitpick threads stay in the editor only until you reload. Select Open in editor on the nitpick in Nitpicks to show it again.

​
Fix with AI

​
Fix with AI only copies to the clipboard

This happens when the extension can’t hand the prompt to an agent, so it copies the prompt instead. Common reasons:
  • coderabbit.agentType is Native, and your editor’s Native behavior is to copy the prompt; see What Native does in each editor.
  • coderabbit.agentType is set to Clipboard.
  • The agent’s extension isn’t installed.
  • coderabbit.agentType is Claude Code Extension, and the Claude Code extension is older than 2.1.0 or is version 3.0.0 or later.
Choose an agent that works in your editor. See Choose your agent.

​
The agent’s extension isn’t installed

The extension shows “You have selected to use … as your AI agent, but the … extension is not installed. Would you like to install it from the marketplace?” This happens when coderabbit.agentType names an agent whose extension isn’t installed. The prompt goes to the clipboard. Select View in Marketplace and install the extension, or change coderabbit.agentType.

​
The Fix with AI icon is missing

This happens when the finding has no instructions for an agent. The icon appears only on findings that include them. Apply the suggestion yourself, or include the finding in Fix all issues. See Fix several findings at once.

​
The agent gets the prompt but doesn’t start

This happens when coderabbit.autoStartTask is off, or when your agent only fills in prompts: Native in Cursor or Windsurf, Claude Code Extension, and Augment Code. Send the prompt in the agent’s chat, or turn on coderabbit.autoStartTask for agents that support it. See Start the agent automatically or review the prompt first.

​
A terminal agent doesn’t run

This happens when the agent isn’t installed on the machine where the extension runs, or isn’t on its PATH. The CodeRabbit terminal for the agent shows an error from your shell instead of starting it. Install the agent’s CLI on that machine, which is the remote machine in a remote window, and check that it runs from a terminal.

​
A finding says Fixed with AI but nothing changed

This happens because the extension marks the finding when it hands the prompt off, even if the agent didn’t make the change or the prompt went to the clipboard. Select Unresolve on the finding in Findings to reopen it.

​
Self-hosted

​
Could not connect to self-hosted instance

This happens when the extension can’t reach your instance’s health check. GET <url>/health must return OK within 5 seconds.
  • Check the URL, and that the instance is reachable from the machine where the extension runs.
  • Open <url>/health in a browser on that machine and check that it shows OK. If that machine has no browser, run curl <url>/health in a terminal there instead.
See Before you begin.

​
The extension connects to CodeRabbit Cloud instead of your instance

This happens when the workspace isn’t trusted, which makes the extension ignore the self-hosted URL, or when CodeRabbit: Logout cleared the URL.

​
The email error shows a wrong Git command

The message “No email provided, either input your email or set it using git config --set user.email” appears when you leave the email empty. The command in the message is wrong. Set your email with:
Then connect again.

​
Reset the extension

If the extension is in a state you can’t explain, reset it:
  1. Run CodeRabbit: Cleanup previous reviews in the workspace. This deletes the stored reviews.
  2. Run CodeRabbit: Logout. With self-hosted CodeRabbit, this also clears your instance URL.
  3. Run Developer: Reload Window.
  4. Sign in again.

​
What’s next

Run a review

Choose a scope and base branch, and see which files a review covers.

Sign in and manage your account

Sign in, choose the organization, and check your plan and review usage.

Network access

See which hosts the extension connects to through firewalls and proxies.