# Send review findings straight to your coding agent

Every review comment has buttons for the coding agents your team uses. Plugins and an MCP server let agents review your branch, fix findings and check again until the review is clean.

[Start free trial](https://app.mergeharbor.com/signup) [Read the docs](https://mergeharbor.com/docs/agent-handoff)

.mergeharbor.yml

```
review:
  coding_agents: [claude_code, cursor]
  fix:
    links: badges # badges | text | off
    fix_all: true
    default_agent: claude_code
    auto_resolve: true
    resolve_threads: true
```

## How it works

1.  ### Choose your agents

    Administrators pick the organization's agents and default. Each person can choose their own default and what the Send button does.

2.  ### Hand off findings

    Send one finding, or every open finding on the pull request, to your agent with the prompt filled in. Nothing runs until you send it.

3.  ### Push the fix

    When your push applies a suggested change or removes the reported code, MergeHarbor marks the finding resolved with the fixing commit.

## What you get

The agents you already use

Claude Code, Cursor, Codex, GitHub Copilot, Conductor, Devin and Windsurf, opened in the editor, app or cloud session you prefer.

All open findings at once

Send all builds one prompt grouped by file, most severe first, up to 60 findings. Or open a fix PR that applies the suggested changes.

Fix until clean

The Claude plugin's explain-findings skill fixes findings, runs your tests and reviews again, stopping after three rounds by default.

Tools over MCP

Agents can list open findings, get a fix plan, apply a suggested change as a patch, mark findings addressed and read team rules.

Signed in as you

Each agent works with your permissions, and hand-off links carry no prompt. The console loads it after checking you can read the pull request.

Cloud agents on your accounts

Devin, Cursor and Copilot cloud sessions start with your organization's or your own key for that agent, so the work runs in your account with the vendor.

Documentation: [Hand off fixes to coding agents](https://mergeharbor.com/docs/agent-handoff) [IDE and agent plugins](https://mergeharbor.com/docs/ide-and-agents) [Integrations](https://mergeharbor.com/docs/integrations)

## Frequently asked questions

Does a hand-off link contain my code?

No. The buttons are short, signed links to the MergeHarbor console. The console loads the prompt only after checking that you can read the pull request.

Who pays for cloud agent sessions?

Your organization or you. Sessions start with a key saved by an administrator or in your personal settings, so the work is billed to and visible in your account with the vendor.

Are comment threads resolved when a finding is fixed?

On GitHub and GitLab, yes. On Bitbucket, Gitea and Azure DevOps, MergeHarbor replies "Resolved in <commit>" instead. A reopened finding is never resolved automatically again.

Have another question? [Ask our support team](https://mergeharbor.com/contact?topic=support)

## Explore other features

### CLI and local reviews

Review your changes before you push

[CLI and local reviews](https://mergeharbor.com/features/cli)

### Codebase-aware review

Reviews that read your codebase, not just the diff

[Codebase-aware review](https://mergeharbor.com/features/review-agent)

### Rules and learning

Plain-English rules and lessons from team feedback

[Rules and learning](https://mergeharbor.com/features/learning)

## Review every pull request with the context of your whole codebase

Connect a code host in minutes. Reviews start right away, and codebase context is added as indexing completes.

[Start free trial](https://app.mergeharbor.com/signup) [Book a demo](https://mergeharbor.com/contact?topic=sales&source=demo)