# GitHub Agent Merge: Cloud PR Fixes, Max Reviews and Approval Controls

Copilot can now keep pull requests moving on GitHub, but fixing blockers and authorizing a merge remain separate decisions.

By Paras Madan | 2026-10-28


GitHub brought Agent Merge to pull requests on github.com on October 28. Copilot can watch for failed Actions workflows and merge conflicts, then attempt repairs in the cloud. Alongside it, Max code review entered public preview and Copilot approvals became generally available.

The practical change is what happens after a first draft. A pull request can become blocked while its author is doing something else. These features bring more of that follow-through into GitHub, with different controls for repair, review and merge.

## How Agent Merge works

In the pull request merge box, select Watch and fix and choose failed workflows, conflicts, or both. The [Agent Merge announcement](https://github.blog/changelog/2026-10-28-agent-merge-watches-and-fixes-pull-requests-in-the-cloud/) also describes an account setting that enables it for future pull requests. Access requires a paid Copilot plan and applicable organizational permissions.

**Agent Merge does not switch on auto-merge.** The latter is a separate setting that merges only after the repository's requirements pass. Repairing a failing check and deciding that a change should ship are different responsibilities.

The [implementation documentation](https://docs.github.com/en/copilot/how-tos/copilot-on-github/use-copilot-agents/watch-and-fix-pull-requests) adds important restrictions: fork-origin and stacked pull requests are unsupported, and the repository's automations policy must be enabled. Repairs use an Actions-based development environment, not the newly announced cloud sandbox. Existing setup steps, repository instructions and skills therefore matter.

## Max review and approvals are different features

[Max review](https://github.blog/changelog/2026-10-28-copilot-code-review-merge-with-confidence-with-max-and-approvals/) uses independent reviewers across models, followed by an agent that reconciles their findings. It costs more AI credits and takes longer than Lite or Balanced. Max is a preview; approvals are GA. Both are offered on Pro, Pro+, Max, Business and Enterprise plans.

Approvals are disabled by default. Administrators can enable them and restrict the file paths Copilot may approve. Once enabled, a Copilot approval can satisfy required-approval counts. Pushing another commit dismisses that approval.

This is a consequential policy choice. A team might accept automated approval for generated documentation but retain human ownership of authentication changes. A broader review mode is not evidence that every risky change has been understood.

## What to test before enabling it broadly

Start with a repository whose CI failures are reproducible and whose setup instructions are accurate. Check whether repairs address the underlying failure rather than weakening an assertion, and review the resulting diff before merging.

The useful outcome is less time spent returning to routine blockers. The wrong success metric would be simply counting how many pull requests merged without a person looking at them.

I'm Paras. I work at the intersection of AI, engineering and distribution.

I help technical teams turn product updates and engineering decisions into stories developers can understand and share.

[Book a 30-minute call](https://cal.com/paras-madan/30min)