Agents
GitHub Agent Merge: can Copilot fix your pull requests while you work?
GitHub's Agent Merge can watch a pull request for failed Actions workflows and merge conflicts. Here's how it works, what it costs, and its limits.
A pull request is ready for review when a GitHub Actions workflow fails. Before you finish investigating, the base branch changes and a merge conflict appears. GitHub's Agent Merge is designed to watch for those blockers and start working on them while you move on to something else.
On October 28, GitHub brought Agent Merge directly to the pull request merge box on github.com. Copilot can watch for failed Actions workflows, merge conflicts, or both. It works in the background when a selected blocker appears; you still need to review its changes and satisfy the repository's merge requirements (GitHub).
What Agent Merge does
On GitHub, Agent Merge is part of Copilot in the cloud. Enable it on a pull request, select the blockers you want it to handle, and Copilot starts a repair attempt when it detects one. GitHub posts updates in the pull request timeline explaining why the agent started (GitHub Docs).
| Blocker | What Copilot is allowed to do |
|---|---|
| Failed GitHub Actions workflows | Investigate and attempt a fix |
| Merge conflicts | Attempt to resolve conflicts between the pull request branch and its base branch |
A repair attempt is not a guarantee. A test might fail because of a bad assertion, a dependency issue or a real regression; a conflict can involve two valid changes whose intended behavior is not obvious from the text alone. Check the resulting diff and rerun or inspect the relevant checks before accepting the change.
How to enable it on GitHub
You need a paid Copilot plan with access to Copilot in the cloud. If your access comes through an organization or enterprise, its policies must allow the cloud feature. The repository's Enable automations Copilot policy must also be enabled (GitHub Docs).
- Open the pull request on GitHub.
- In the merge box, select Watch and fix.
- Choose Fix failed Actions workflows, Resolve merge conflicts, or both.
- Follow the Agent Merge updates in the merge box and pull request timeline.
- Review any changes Copilot makes and check the workflow results.
You can also enable it by default for pull requests you create under Settings → Copilot → Cloud. To stop it on an individual pull request, select Unassign Copilot in the merge box. GitHub says the feature does not support stacked pull requests or pull requests opened from forks.
Does Agent Merge merge the pull request?
The GitHub cloud feature prepares and maintains the pull request; enabling it does not turn on auto-merge. GitHub's separate auto-merge feature can be combined with Agent Merge and will merge once the repository's required reviews and checks are satisfied (GitHub Docs).
The distinction matters: if auto-merge is enabled, a successful repair can be followed by a merge as soon as the configured requirements are met. Review the repository rules and the proposed changes rather than assuming there will always be another manual confirmation.
The Copilot app has a different experience. GitHub says its app version can also address review comments and can merge the pull request once GitHub allows it. VS Code also documents an experimental Agent Merge experience with its own options. Those surfaces should not be treated as identical to Watch and fix on GitHub (GitHub Docs; VS Code).
What does it cost?
Agent Merge's cloud feature requires a paid Copilot plan. Its AI credit usage is charged to the person who enabled it on the pull request, who may not be the pull request's author. GitHub does not state a fixed cost per repair in its Agent Merge documentation; usage depends on the work and models involved (GitHub Docs).
GitHub's individual billing documentation lists Copilot Pro at $10 per month, Pro+ at $39 and Max at $100, with different included AI credit allowances. Those are plan prices, not Agent Merge charges; the amount a repair consumes is separate usage within the applicable allowance and billing rules (GitHub billing). Check your usage dashboard and plan terms before enabling it broadly.
Where do the fixes run?
Although Agent Merge belongs to Copilot in the cloud, GitHub says its fixes run in a GitHub Actions-based development environment, not a cloud sandbox. It can use repository custom instructions, agent skills and setup steps in .github/workflows/copilot-setup-steps.yml (GitHub Docs).
That makes the repository's setup relevant to the result. A missing dependency or an inaccurate instruction can affect what the agent sees. Pay particular attention to changes affecting tests, permissions and workflow configuration: a green check is useful, but it does not prove that the original intent or security of the workflow was preserved.
Our take
Agent Merge targets a familiar source of friction: waiting for checks, noticing a failure and returning to a branch just to make it mergeable. For a solo developer or small team, a background repair could shorten that interruption.
Its value will depend on the quality of the proposed fixes and the time needed to verify them. Start on a pull request with clear checks, choose only the blocker types you want handled, and compare the agent's diff with the original goal. Track credit usage alongside review time. The meaningful result is a correct, maintainable change that passes the right checks—not simply a green merge box.
Sources
- GitHub, Agent Merge on pull requests, October 28, 2026
- GitHub Docs, getting pull requests ready with Agent Merge, checked October 29, 2026
- GitHub Docs, managing pull requests in the Copilot app, checked October 29, 2026
- VS Code, Agents window, checked October 29, 2026
- GitHub Docs, individual Copilot billing, checked October 29, 2026
Spotted an error in this article? Report it · Our corrections policy
