# Hand off fixes to coding agents

> Send one finding, or every open finding on a pull request, to Claude Code, Cursor, Codex, Copilot or Devin in one click, or apply them as a fix pull request.

## One-click hand-off

Each inline comment ends with small **Send to …** buttons, one for every coding agent your organization uses. The review summary adds a **Send all to …** line that hands over every open finding of the pull request together.

The buttons are short, signed links to the MergeHarbor console. The prompt is never in the link: the console loads it after checking that you can read the pull request, then opens your agent with the prompt filled in. Nothing runs until you send it.

| Agent          | What the button opens                                                                                                        |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Claude Code    | Claude Code in your terminal (in the repository's folder), the VS Code extension, the desktop app, or Claude Code on the web |
| Cursor         | Cursor's agent chat, or a Cursor cloud agent on the pull request's branch                                                    |
| Codex          | The Codex app, matched to your checkout by its Git remote                                                                    |
| GitHub Copilot | Copilot in VS Code, or a Copilot cloud agent task                                                                            |
| Conductor      | A new Conductor workspace                                                                                                    |
| Devin          | A Devin session                                                                                                              |
| Windsurf       | The prompt to paste into Cascade (Windsurf has no prompt link)                                                               |

When a prompt for all findings is too long for an agent's link, the link carries a short prompt that asks the agent to read the findings through the [MCP server](https://mergeharbor.com/docs/integrations#coding-agents-mcp) instead, and the console shows the full prompt to copy.

## All open findings at once

**Send all** builds one prompt (or one agent session) for every open finding of the pull request. Dismissed and resolved findings are left out. Findings are grouped by file, the files ordered by their most severe finding, up to 60 findings per prompt.

To skip the editor entirely, a **fix PR** applies the suggested changes in a pull request against your branch, which you can review and merge from the console.

## Cloud agents

Devin, Cursor cloud agents and GitHub Copilot tasks run in the vendor's cloud. MergeHarbor starts each session with **your organization's or your own** API key, so the work is billed to, and visible in, your account with the vendor. MergeHarbor never uses a key of its own.

**For the whole organization** (administrators, **Settings → Coding agents → Organization setup**):

1. Create the key with the vendor. For Devin, create a service key (it starts with `cog_`) in Devin's settings and note your Devin organization id (it starts with `org_`).
2. Save it, then use **Test connection** to check it. MergeHarbor makes a read-only call; no session starts.
3. Once a key is saved, every member sees that agent's **Send to …** buttons on review comments. By default anyone who can read a pull request can start a session with it; you can limit it to people with the `pulls.fix` permission.

**For yourself** (**Your coding agent (account menu)**): save your own key to use it instead of the organization's.

Keys are encrypted at rest, shown only by their last four characters, and every save, test and removal is in the audit log.

## Your default agent

Administrators choose the organization's agents and default under **Settings → Review behaviour**. Each person can pick their own default agent and what the **Send** button does (copy the prompt, open the agent, or start a cloud session) under **Your coding agent (account menu)**, or from the agent menu at the top of the Pull requests page. On a pull request, press **F** to hand off all open findings.

## Findings close when you push the fix

When you push to a reviewed pull request, MergeHarbor checks each open finding whose lines your commits changed:

- the suggested change was applied, or the reported code is gone: resolved;
- the code around it changed but the reported lines are still there: resolved only if the review of your push read that change and did not report the issue again (no extra model calls).

Resolved findings are marked in MergeHarbor with the commit that fixed them, and their comment threads are resolved on GitHub and GitLab. On Bitbucket, Gitea and Azure DevOps MergeHarbor replies "Resolved in <commit>" instead. A finding that someone reopens is never resolved automatically again.

The review settings control this:

```yaml
review:
  coding_agents: [claude_code, cursor]
  fix:
    links: badges # badges | text (for mirrors that block images) | off
    fix_all: true # hand-off line for all open findings in the summary
    default_agent: claude_code
    auto_resolve: true # resolve findings a push fixes
    resolve_threads: true
```

## Analytics

Every launch is recorded: which finding went to which agent, and whether it was resolved afterwards (and by which commit). **Agent hand-off outcomes** in analytics shows, per agent, how many findings were sent and how many were fixed.