THE SIGNAL IN ONE SENTENCE
A coding agent can now work through several common reasons a pull request is not ready, while new session controls help a person supervise several agent jobs.
01
WHAT ACTUALLY CHANGED
GitHub introduced Agent Merge in public preview through Visual Studio Code. The agent can resolve review feedback, investigate failed checks, and work through merge conflicts to prepare a pull request for a final merge decision.
The same release adds hierarchical chat sessions that group related conversations and show which sessions need attention. Experimental multi-root workspaces can bring Copilot and Claude agent sessions to every folder in a larger workspace.
GitHub also says the Copilot app and command-line interface now honor content exclusions. Organizations can designate sensitive code that should not be placed in the model context during agent workflows.
These changes address two different production problems. Agents need enough freedom to perform the tedious integration loop, while supervisors need a concise view of what is blocked and administrators need enforceable boundaries around which code the system may inspect.
02
WHY THIS MATTERS
Generating the first version of code is increasingly the easy part. Pull requests accumulate reviewer notes, stale branches, merge conflicts, dependency failures, and one test that appears to run on spite. Integration is where useful automation either earns trust or creates a second job for the reviewer.
Agent Merge places the system closer to the point where code becomes real. That increases its usefulness and the importance of repository rules, protected branches, required checks, content exclusions, and a human who understands what the final green badge means.
The session hierarchy may sound like interface housekeeping, but it points toward the actual future of agent supervision. People will not read every transcript. They need a control surface that tells them which jobs finished, which are uncertain, and which require judgment.
03
WHERE IT COULD HELP
- Resolve straightforward pull-request feedback
- Diagnose and repair failing checks
- Reconcile merge conflicts before human review
- Track several coding-agent sessions without rereading every transcript
KEEP A HAND ON THE WHEEL
Agent Merge remains in public preview, and GitHub has not published independent success rates across real repositories. Teams should preserve protected branches, inspect meaningful changes, verify excluded paths, and test how the agent behaves when review instructions conflict.
04
TERMS WORTH KEEPING
OPEN GLOSSARY CARD
Agent session
One continuing record of an agent task, including its context, actions, and results.
OPEN GLOSSARY CARD
Required approval
A repository rule that blocks a code change until a defined number of reviewers approve it.
OPEN GLOSSARY CARD
Regression test
A repeatable check that reveals whether a change broke behavior that previously worked.
SOURCES AND VERIFICATION STATUS
This article was written from the materials below. Product claims and dates were checked against those sources on September 4, 2026.
PUBLICATION RECEIPT: Revision 1. Approved by Zak and published September 4, 2026.
THE PUBLICATION ENGINE
WANT A SIGNAL OF YOUR OWN?
We build source-grounded publications, private briefings, and editorial systems for organizations with something useful to say.
WORK WITH US