GitHub Copilot in Visual Studio: Git Agent Can Now Explore Pull Requests

GitHub CopilotOct 22, 2026View original changelog

The Git agent in GitHub Copilot Chat for Visual Studio 2026 can now explore a pull request and return a summary with navigable links to the underlying comments and files. Developers attach a pull request as context from the Git Repository window. The feature needs the Git provider's MCP servers connected, and both GitHub and Azure DevOps are supported.

Key Takeaways

The Git agent in Copilot Chat can now explore a pull request and summarize it for the developer.
Summaries include navigable links to the underlying comments and files, so reviewers can jump straight to the details.
A pull request is attached as context from the Git Repository window inside Visual Studio 2026.
The feature requires connecting the Git provider's MCP servers.
GitHub and Azure DevOps are both supported providers.
The update is available on all Copilot plans, from Free through Enterprise.

Understanding a Pull Request Without Leaving Chat

GitHub added a way for the Git agent in GitHub Copilot Chat to explore a pull request inside Visual Studio 2026. Instead of reading through a long pull request by hand, a developer opens GitHub Copilot Chat, selects the Git agent and attaches a pull request as context from the Git Repository window. The agent responds with a summary of the pull request, and that summary includes navigable links to the underlying comments and files. This keeps the developer in the IDE while still giving a quick path into the details that matter.

Requirements and Supported Providers

The capability depends on the Git provider's MCP servers, so those need to be connected before the agent can read a pull request. GitHub and Azure DevOps are both supported. The change shipped in the September 2026 update for GitHub Copilot in Visual Studio, and that update is available on all Copilot plans, including Free, Student, Pro, Pro+, Max, Business and Enterprise.

Why It Matters

Pull request review often starts with building context: what changed, what was discussed and which files carry the important edits. A summary with links straight to comments and files shortens that first step. It also fits the broader direction of the Git agent in Visual Studio, which already helps developers check their work before a pull request is opened.