GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

On 28 October 2026 GitHub announced Agent Merge, a feature that lets Copilot watch a pull request and automatically fix whatever is blocking it from merging. It was already in the GitHub Copilot app and Visual Studio Code; it now sits directly in the pull request merge box on GitHub.

How it works

You select “Watch and fix” on a pull request and choose what Copilot may handle: failing Actions workflows, merge conflicts, or both. When one of those blockers appears, Copilot works on it in a cloud development environment. It can be combined with auto-merge, so GitHub merges the pull request once every requirement is met. You can also switch it on by default for all your pull requests from your Copilot settings.

Availability

It is available to users on a paid Copilot plan, subject to organisation and enterprise policies. GitHub’s announcement does not state a preview or GA label, and does not give separate pricing.

What it means

The chore that used to stall a release, a red build or a conflicting branch, is now something an agent handles while the developer is elsewhere. That shortens the wait for working software. It also means an AI agent can push changes to code that is about to ship, with little human attention in between.

So what

If you commission software, ask your development partner three things: is this switched on, which blockers can the agent touch, and does a person still review before anything reaches production? Speed is only an advantage when the review gate survives it. Our AI-assisted development service sets those rules up front. To apply them to your product, start a project.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

Read ›

GitHub Copilot server-to-server authentication: AI agents get their own identity, billed to the organisation

GitHub put Copilot server-to-server authentication into public preview on 27 October 2026, letting AI agents built with the Copilot SDK run as a GitHub App rather than as a signed-in developer. For anyone buying AI software development, it means automated AI work can be tracked and billed per organisation.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work