Playbooks · Teams
Copilot Agent Merge: watch a PR and fix its blockers
Written November 13, 2026
Agent Merge watches a pull request and fixes what blocks it — failed checks or conflicts. The gates, the approval rule, and what it won't touch.
What changed
Agent Merge existed in the GitHub Copilot app and in Visual Studio Code first. On October 28, GitHub integrated it into pull requests on GitHub.com. Select Watch and fix in a pull request's merge box, and Copilot keeps watch over that pull request. When a blocker you selected appears, Copilot starts work in a cloud development environment to clear it. It is a standing watch rather than a one-off command: the point is that the failure at 4 p.m. gets attention without anyone re-asking.
A walkthrough of the button is not the hard part. The decision a team lead actually faces is whether the gates around it are set the way they think, and whether one nearby setting, Copilot's own approval, has quietly been given merge power. Those are the two cells this page is about.
The blockers it can fix
GitHub's Agent Merge documentation gives you exactly two kinds of blocker to hand over, chosen per pull request:
- Fix failed Actions workflows: Copilot investigates a failing GitHub Actions workflow and works on a fix.
- Resolve merge conflicts: Copilot resolves conflicts between the pull request's branch and its base branch.
You can pick either one or both. When Copilot starts, an update appears in the Agent Merge section of the merge box and as a timeline event explaining why it started. Behind the scenes, the fixes run in a GitHub Actions-based development environment rather than a cloud sandbox, using the repository's own setup steps file, custom instructions, and agent skills. You can also turn Agent Merge on by default for pull requests you create, under Settings, Copilot, Cloud. To stop it on one pull request, click Unassign Copilot in the merge box. One cost note from the docs: the AI credits Agent Merge uses are charged to the person who enables it for the pull request, who is not necessarily the author.
The gates before it runs
- A paid Copilot plan with access to Copilot in the cloud. Agent Merge is part of that cloud surface.
- Organization and enterprise policy must allow the use of Copilot in the cloud. The changelog puts availability subject to those policies, and the docs repeat the condition.
- The repository's Enable automations policy must be enabled. Without it, the watch has no standing in that repository.
- Shape limits: Agent Merge does not support stacked pull requests, or pull requests opened from a fork.
The approval rule that matters
Agent Merge gets a pull request ready; it does not supply the approvals a branch rule demands. GitHub's docs are plain that it does not replace your review or the repository's merge requirements, and that human review of Copilot's fixes is still needed before merging. It also combines with auto-merge without enabling it: Agent Merge clears blockers, auto-merge merges once all required reviews and status checks pass, and turning on the first leaves the second exactly as it was.
The separate question is whether a Copilot approval itself can count toward those required approvals. That is a different feature, Copilot code review's auto-approval, and GitHub's configuration documentation shows it as an admin-set stack, off unless someone turns it on:
- At repository level, under Auto-approval: Allow Copilot to approve pull requests, and Allow Copilot approvals to count toward merge requirements. An optional File paths list takes one glob per line, up to 15, and an approval counts only when every changed file in the pull request matches one of the globs.
- At organization level, the choices are Enabled everywhere, Let repositories decide, Enable for selected repositories, or Disabled everywhere.
- At enterprise level, Allow Copilot to approve pull requests is a policy that organizations sit under.
So the answer for a team lead is concrete: Agent Merge cannot approve anything. If Copilot approvals count in your repositories today, someone in the admin stack set that switch, and the file-path list is the dial that narrows where it applies. The wider decision is framed in Decide whether Copilot should approve PRs.
What it won't touch
The blockers Agent Merge can act on are the two you select: failed workflows and merge conflicts. Review comments are not in that list on GitHub.com today, so a pull request blocked on a reviewer's requested changes waits for a human or another tool, not for the watch. And because the fixes arrive as new commits from an agent, they deserve the same read as any other contributor's push, especially where a workflow fix could mean a weaker test rather than a repaired one.
Related playbooks
- Copilot Fable 5.2: check ZDR before enabling
- Run work that spans several repos in one Copilot Project, and keep computer use on a short leash
- Set team plugin defaults for Copilot
- Decide whether Copilot should approve PRs
Sources
- Agent Merge watches and fixes pull requests in the cloud — GitHub Changelog
- Getting pull requests ready to merge with Agent Merge — GitHub Docs
- Configuring code review by GitHub Copilot — GitHub Docs
Back to: Teams playbooks hub · Also: Decide whether Copilot should approve PRs · Copilot's model-policy API is GA at four levels