Work with findings in JetBrains IDEs

When a review runs, its findings appear in the CodeRabbit tool window, and open findings also appear as markers in the editor. From a finding, you can go to the code, apply the suggested change, hand the fix to a coding agent, or ignore it.

​

Browse findings

The results area has a header and two panes:

• The header shows the Review menu for saved reviews, how many findings are resolved, and the Fix all, Review again, and New review buttons.
• The list groups findings by severity: Critical, Major, Nitpick, and Info. Minor and trivial findings both appear under Nitpick. Each finding shows its title and its file and line.
• The Finding details pane shows the finding you select: its severity, title, location and status, CodeRabbit’s comment, the Affected code, and the Suggested fix or Fix guidance.

To narrow the list, select Filters, then filter by status (Open or Resolved), by severity, or by text in titles, details, and file paths. Resolved covers findings you applied or ignored. Clear filters shows every finding again. The details pane has Apply suggestion, Fix with AI (or Copy fix prompt), and More actions, which holds Open in editor, Show diff, Ignore, Reopen, and Feedback.

​

Go to a finding in the editor

To open the code, select the location link in Finding details, or choose More actions → Open in editor. Selecting a finding in the list only shows its details. Every open finding of the review shown in the tool window also gets a gutter icon, a highlight on its lines, and a mark on the editor’s scroll bar. Hover over the gutter icon to see the finding’s title, and select it to open a popup with the details and the Show diff, Apply suggestion, Fix with AI, and Ignore buttons. Markers go away when you apply or ignore the finding. The editor uses the IDE’s error, warning, and information styles: Critical findings show as errors, Major findings and minor nitpicks as warnings, and trivial nitpicks and Info findings as information. Show diff opens a diff window that compares the Reviewed code with the Suggested code. It shows the code as it was when CodeRabbit reviewed it, not your current file.

​

Apply a suggestion

Apply suggestion replaces the reviewed lines with CodeRabbit’s suggested code as a single edit, and marks the finding Applied. It doesn’t save the file, so you can check the change first. Undo (Ctrl+Z on Windows and Linux, Cmd+Z on macOS) reverts the edit and reopens the finding. The plugin applies a suggestion only when it can do so safely. Otherwise it shows why: If a finding has more than one suggestion, the plugin applies the first one. You can also apply suggestions from a saved review, as long as the lines haven’t changed since.

​

Ignore or reopen a finding

Ignore marks a finding Ignored, and Reopen marks an ignored or applied finding Open again. There’s no separate resolve action: a finding counts as resolved once you apply or ignore it. These statuses stay on your computer, saved with the review. CodeRabbit doesn’t receive them, they don’t change your pull request reviews, and a later review can report the same issue again. To tell CodeRabbit that a finding is wrong, give feedback.

​

Fix with AI

Fix with AI hands a finding to a coding agent. The Fix findings with setting in Settings → Tools → CodeRabbit picks the agent: For the three agents, the plugin builds a prompt from the finding’s title, comment, guidance, and suggested code, and tells the agent to check the finding against the current code before it edits. The prompt is copied to the clipboard too, so you can paste it if the agent doesn’t start. Each Fix with AI opens a new terminal tab. Claude Code and Codex start an interactive session with the prompt, so you can follow up in the same tab; opencode runs the prompt once and exits. The plugin adds no permission flags, so the agent’s own approval prompts and settings apply. The agent must be installed and on the PATH of the shell that the IDE’s terminal uses; in Remote Development, that’s the host. The plugin doesn’t check this; if the agent is missing, the terminal shows the shell’s “command not found” error. On macOS and Linux, a long prompt goes through a temporary file named coderabbit-fix-*.txt, which is deleted when the agent exits without an error. Fix with AI doesn’t change a finding’s status. After the agent finishes, select Review again to check the fix. Fix with AI sends nothing to CodeRabbit; your agent’s own terms apply to what you send it. It’s also separate from CodeRabbit’s Coding Agent, which runs tasks in the cloud.

​

Fix several findings at once

Fix all opens “Select findings to fix”, which lists the open findings with all of them selected. Clear the ones to skip, then select the button, such as Send 4 findings to Claude Code or Copy prompt for 4 findings. You can send up to 50 findings at a time.

​

Give feedback on a finding

To tell CodeRabbit that a finding is wrong, choose More actions → Feedback. In “Send finding feedback”, pick a Reason (Not helpful, Incorrect, Poorly formatted, Wrong lines, or Suggestion is invalid), optionally add details of up to 4,000 characters, and select Send feedback. The feedback includes the finding’s file path and comment.

​

Review history

The plugin saves each completed review of a repository on your computer, and keeps the newest 20. Cancelled, failed, and skipped reviews aren’t saved. To open a saved review, pick it from the Review menu in the results header. Saved reviews are listed by date and branch, and Current review returns to the latest one. After you reopen a project, the tool window shows the newest saved review once you’re signed in. In a saved review, you can still apply, ignore, reopen, fix, and give feedback on findings. Saved reviews hold the findings, their statuses, and the reviewed lines, but not full files. They’re stored in the project’s workspace file, usually .idea/workspace.xml, and nowhere else. If that file is committed to version control or included in a shared backup, others can read the saved reviews, so keep it out of both. In Remote Development, they’re stored on the remote host. To delete them, choose Clear local review history… from the Options menu (⋮) in the tool window’s title bar, then Clear history. This deletes the saved reviews of the current repository only, and can’t be undone. Signing out, switching organizations, and uninstalling the plugin don’t delete them.

​

What’s next