GitHub Copilot in Visual Studio gets debugger agent and cloud agent sessions from the IDE
GitHub Copilot in Visual Studio received an April update bringing the ability to launch cloud agent sessions directly from the IDE, user-level custom agents, and a new debugger agent that reproduces bugs through live runtime execution and automatically validates fixes.
GitHub Copilot in Visual Studio received a set of agentic upgrades with which Microsoft aims to bridge the gap between the web interface and the local development environment.
What does GitHub Copilot change in the VS workflow?
The key change is the ability to launch cloud agent sessions directly from the IDE — previously, developers had to leave Visual Studio and open the GitHub web interface in a browser. Now the entire agentic workflow stays within a single tool.
In addition, the update introduces user-level custom agents. Previously, custom agents were tied to an individual workspace (project), but now they are defined at the user level and are available across all projects.
How does the new debugger agent reproduce and validate bugs?
The debugger agent — the headline feature of this update — works through live runtime execution: when a developer reports a bug, the agent independently reproduces the issue by running the code in a real environment. After proposing a fix, it runs the same scenario again to confirm the error no longer exists.
This approach differs from previous static code analysis because it relies on runtime state, not just source code analysis.
Other changes in the April update
The update also brings two smaller but useful features.
Customizable keyboard shortcuts allow tailoring shortcuts for Copilot actions within the VS environment, reducing friction in day-to-day use.
The Chat history panel provides an overview of previous conversations with Copilot, enabling developers to find earlier generated suggestions or answers faster without re-asking the same questions.
Context: Copilot’s agentic development direction
Microsoft’s consistent direction over the past several update cycles is transforming Copilot from a code completion tool into an orchestrated agent capable of independently planning and executing more complex tasks. Integrating cloud agent sessions directly into the IDE reflects that strategy — developers no longer have to choose between local context and cloud agentic capabilities.
The update is available to GitHub Copilot users in Visual Studio starting April 30, 2026.
Frequently Asked Questions
- What is the debugger agent in GitHub Copilot?
- The debugger agent is a new agentic component that reproduces a reported bug by running the code in a live runtime environment, then automatically validates the proposed fix.
- What is the difference between user-level and workspace-level custom agents?
- Workspace-level agents apply only to a single project, while user-level custom agents apply to all projects of the same user within Visual Studio.
This article was generated using artificial intelligence from primary sources.
Related news
ArXiv Odysseys: CMU's realistic web agents benchmark reveals SOTA frontier models achieve 44.5% success and 1.15% Trajectory Efficiency on long-horizon tasks
AWS Bedrock AgentCore: Serverless MCP Proxy with IAM, OAuth 2.0 JWT, and CloudWatch Observability for Enterprise Governance
AWS Bedrock AgentCore Memory: three patterns for namespace-level long-term agent memory with IAM access control