Agent Merge moves pull-request repair into the cloud

A pull request can be conceptually done and still be blocked by a conflict or a failing check. GitHub's Agent Merge brings an agent into that waiting period: it watches the pull request and can start work in a cloud development environment when a selected blocker appears.

The GitHub Changelog says users can choose whether Agent Merge fixes failing Actions workflows, resolves merge conflicts, or does both. It can be enabled from the pull request merge box and combined with auto-merge when the repository's requirements are satisfied.

Repair is not the same as approval

The feature shortens the distance between a detected blocker and a proposed repair. It does not answer whether the repair is the right change, whether the failing test exposes a deeper design issue, or whether the pull request should be merged. Those remain review decisions.

An agent can keep a pull request moving without becoming the owner of the decision to merge it.

Teams should begin with low-risk blockers, preserve the agent's evidence in the pull request, and keep branch protection and review requirements intact. The cloud environment is useful precisely because the repair can be inspected before it becomes history.