coderabbit.autoStartTask, or choose another agent.
This is different from CodeRabbitâs , which runs in CodeRabbitâs cloud, and from Fix with AI in CodeRabbit Security. See Names that collide.
Choose your agent
Setcoderabbit.agentType to the agent you use; see Open the settings. The default is Native.
Requirements by agent type:
- Terminal agents (
Claude Code,Codex CLI, andopencode) run in the editorâs integrated terminal, which stays open for the next handoff. The command runs right away:claudeandcodexstart an interactive session with the prompt, andopencode runruns the prompt once. If the agent from the previous handoff is still running in that terminal, the extension types the new command into it as input; exit the agent or close the terminal first to start a fresh run. The extension adds no permission flags, so the agentâs own approval prompts apply. The agentâs CLI must be installed and on yourPATHon the machine where the extension runs, which is the remote machine in a remote window. The extension doesnât check for it: if the CLI is missing, the terminal shows your shellâs error, and the finding is still marked âFixed with AIâ. - Extension agents (
Claude Code Extension,Cline,Roo,Kilo Code, andAugment Code) need that agentâs extension. If itâs missing, the extension offers View in Marketplace.Claude Code Extensionneeds Claude Code extension version 2.1.0 or later, below 3.0.0.
coderabbit.agentType and coderabbit.autoStartTask apply, so a repository you clone canât choose which agent runs or whether it starts on its own. See Restricted Mode.
What Native does in each editor
To have an agent start on its own in Cursor, Windsurf, or the other editors, choose a terminal agent, or
Cline, Roo, or Kilo Code with coderabbit.autoStartTask on.
Start the agent automatically or review the prompt first
coderabbit.autoStartTask is on by default. It decides whether Native in VS Code, Cline, Roo, and Kilo Code start right away. Turn it off to read or edit the prompt before the agent runs.
Fix one finding
1
Open the finding in the editor
In Findings or Nitpicks, select Open in editor on the finding.
2
Select Fix with AI
Select the sparkle Fix with AI icon in the comment threadâs title bar. The icon appears only when the finding includes instructions for an agent.
3
Check the change
The agent edits your files. Review the change, then review again to check it.
Fix several findings at once
After a review completes with unresolved findings, Findings shows a Fix all issues button:- Select Fix all issues.
- Choose Select files or Select comments.
- Pick the files or findings to fix.
Review, fix, and review again
- Make changes, yourself or with an agent, and commit. With
coderabbit.autoReviewModeset toauto, every new commit starts the automatic review unless you cancel it, including commits an agent makes in a terminal. Withprompt, a commit starts a review only when you answer Yes to the notification. - Hand the findings to your agent with Fix with AI or Fix all issues.
- Review again. An automatic review starts only after a commit and covers committed changes, so commit the agentâs edits, or start a review yourself with Uncommitted changes to check them before you commit. The next review covers only what changed since the last one. After an amend or a rebase, it covers the whole branch. See Review again after more changes.
Whatâs next
Work with findings
Apply suggestions yourself, ignore findings, or reopen ones the agent didnât fix.
Agent skills for the CLI
Let your coding agent run CodeRabbit reviews itself with CodeRabbit skills.
Troubleshooting
Find out why a handoff only copied to the clipboard or the agent didnât start.