GitHub Copilot: New SDK-Powered Agent in Visual Studio (Preview)
GitHub introduced a new agent option, in public preview, inside GitHub Copilot Chat for Visual Studio, built on the same GitHub Copilot SDK that powers Copilot CLI. The agent is tuned to get more tasks right on the first attempt, trading verbose back-and-forth for concise, scannable responses. It ships in the Visual Studio 2026 Stable Channel and is available on every Copilot plan, letting developers start work in the CLI, the GitHub Copilot app, or VS Code and pick it back up seamlessly inside Visual Studio.
Key Takeaways
- GitHub shipped a new SDK-powered agent in Visual Studio's Copilot Chat, in public preview, aimed at getting tasks right on the first attempt.
- The agent runs on the GitHub Copilot SDK, the same runtime behind Copilot CLI, communicating over JSON-RPC with packages for TypeScript, Python, Go, .NET, Java, and Rust.
- Responses are shorter and more scannable, reducing the back-and-forth developers previously needed to steer the agent.
- It's designed for everyday work — feature changes, bug fixes, and refactors — not just complex agentic tasks.
- GitHub is pitching this as part of a cross-surface consistency push, letting work started in the CLI or the Copilot app continue seamlessly in Visual Studio.
- The new agent is available on every Copilot plan, accessed directly from the existing agent picker with no separate signup required.
Sources & Mentions
3 external resources covering this update
Overview
GitHub's July 2026 Visual Studio update added a new agent to Copilot Chat's agent picker, listed as Agent (Preview). Unlike Visual Studio's existing agent mode, this one is built directly on the GitHub Copilot SDK — the same programmatic runtime that powers the GitHub Copilot CLI. GitHub describes the SDK as a programmatic interface to the Copilot CLI agent runtime, handling planning, tool invocation, and file edits, and communicating with a Copilot CLI server over JSON-RPC. The SDK ships packages for TypeScript, Python, Go, .NET, Java, and Rust, and Visual Studio's new agent is the first IDE surface to run on top of it directly.
Why It Matters
GitHub says the new agent is designed to get more tasks right the first time, reducing the back-and-forth developers previously needed to keep an agent on track. Its responses are also shorter and easier to scan, aimed at cutting down the time developers spend reading agent output rather than reviewing the actual code change. It's intended for the kind of day-to-day work developers already hand off to Copilot: feature changes, bug fixes, and refactors.
A Shared SDK Across Copilot Surfaces
Because the new agent runs on the same SDK as Copilot CLI, GitHub frames this as a step toward consistency across Copilot surfaces. Developers can start a task in the CLI, the GitHub Copilot desktop app, or VS Code, and continue that same work inside Visual Studio without losing context or switching mental models between tools.
Getting Started and Availability
To try it, developers open GitHub Copilot Chat in Visual Studio, click the agent picker at the bottom of the chat window, and select Agent (Preview). The new agent is available to every Copilot plan tier. It shipped alongside other changes in the same July update, including built-in .NET and Azure skills and organization-level custom instructions for Business and Enterprise customers, though those are separate, admin-facing additions.