By ByteBot
Copilot has been writing code for two years. It just learned to ship it.
VS Code 1.136, released September 2, arrived with Agent Merge in public preview — a feature that runs a supervision loop on your open pull requests until every blocker is cleared. Review comments get answered. Failing CI checks get fixed. Merge conflicts get resolved. Then it checks again, because new blockers can appear after each fix. It loops until the pull request is genuinely ready to land, not just superficially untouched.
It Is a Loop, Not a Pass
Most coverage of Agent Merge describes it as a tool that “fixes” your PR. That framing undersells what it actually does and sets up the wrong expectations. Agent Merge runs a repeating cycle: address unresolved review threads → fix failing required CI checks → resolve merge conflicts from base branch movement → rerun workflows → repeat from the top. Each iteration can expose new issues the previous fix introduced, and the agent handles those too.
That design choice matters. A one-shot fixer would stall on any PR where a reviewer leaves a follow-up comment after the first round of fixes — which is most PRs. The loop model means Agent Merge keeps working until the state is actually clear, not until it ran once.
How to Enable Agent Merge
Agent Merge is off by default and invisible until you explicitly turn it on. Open VS Code Settings and enable chat.agentMerge.enabled. Then, for a specific session, either run “Enable Agent Merge for Active Session” from the Agents window or click the Agent Merge button in the title bar.
Both steps are required. The setting makes the feature exist. The session-level enable attaches it to an active PR. Without the second step, nothing happens even with the setting on. Agent Merge is available on Copilot Pro+, Max, Business, and Enterprise — not the free plan.
// settings.json
{
"chat.agentMerge.enabled": true
}What Agent Merge Cannot Do
Agent Merge automates the mechanics, not the governance. That is a hard technical limit that matters for anyone running repos with strict branch protection.
If your repository requires two human reviewers, Copilot cannot satisfy that requirement. It goes further: when Copilot’s coding agent opens a pull request under its own identity, GitHub enforces a rule requiring one additional approval beyond whatever your policy specifies. A repo requiring one approval now effectively requires two before Copilot’s PR can merge. Admins can disable this, but it is on by default.
Two related restrictions: approvals from developers who collaborated with Copilot on the changes do not count toward required review thresholds — GitHub treats those as compromised for the approval gate. And Copilot cannot mark its own draft pull requests as ready for review; that step must come from a human.
The practical upshot: Agent Merge excels on repos where merging is gated on CI passing and review feedback. It struggles on repos where mandatory human sign-off counts block the path. Enterprise teams with strict governance policies still need a human in the merge loop.
The Rest of VS Code 1.136
Agent Merge is the headline, but it ships alongside infrastructure that matters. The Agent Host is a new dedicated process that isolates agent sessions from the extension host — sessions now survive closing VS Code. The Agent Host Protocol (AHP) is an open JSON-RPC spec letting third-party agent runtimes, including the Claude Agent SDK, plug into VS Code through a standard interface. Microsoft published AHP client libraries in Rust, TypeScript, Go, Kotlin, and Swift. Multi-root workspaces landed experimentally, letting Copilot and Claude agents operate across multiple project folders simultaneously.
AHP deserves more attention than it is getting. Microsoft is turning VS Code into an agent runtime that any harness can target — not just Copilot. That is a platform play with consequences well beyond this release.
The Workflow Shift That Actually Happened
In March 2026, Copilot Coding Agent went generally available and the headline was: AI can go from GitHub issue to open pull request without human intervention. The gap it left was everything between “PR opened” and “PR merged” — review rounds, CI reruns, rebasing — which landed back on the developer.
Agent Merge closes that gap. The loop now runs: agent writes code → agent opens PR → agent handles review iterations → developer reviews the final state and decides whether to merge. Code review does not disappear. It changes shape. Instead of explaining to Copilot what is wrong with each iteration, your job becomes evaluating whether what ultimately shipped is what you actually wanted.
That is a genuine workflow change. The limits around required human approvals mean it will not work seamlessly everywhere. But the direction is clear: agents are moving from writing code to shipping features, and “PR merged” is now part of their scope. Enable the setting, attach it to a session, and see how much of your PR review queue you stop touching.
