GitHub Copilot in Visual Studio: Cloud Agent Integration
GitHub CopilotGitHub Copilot's Visual Studio April 2026 update brings Cloud Agent Integration directly into the IDE, enabling developers to launch remote coding sessions without leaving Visual Studio. By selecting "Cloud" from the agent picker in the Chat window and describing a task, the cloud agent clones the repository, executes the work on GitHub Actions infrastructure, and opens a pull request — all while the developer continues working locally or closes the IDE entirely. Visual Studio then sends a notification with a direct link to the resulting PR. The feature requires a GitHub repository with Copilot issue-creation permissions enabled.
Sources & Mentions
5 external resources covering this update
Visual Studio April Update – Cloud Agent Integration
Visual Studio Blog
VS 2026 Joins VS Code with Integrated Cloud Agent: Assign a Task, Close the IDE, Get a PR
Visual Studio Magazine
Visual Studio cloud agents now run inside GitHub Copilot
Help Net Security
Visual Studio 2026 gets cloud agent integration
Heise Online
Visual Studio April update adds autonomous cloud agents and a new debugger agent
Neowin
Cloud Agent Integration in Visual Studio
The April 2026 update to GitHub Copilot in Visual Studio introduces one of the most significant workflow changes in the IDE's agentic roadmap: the ability to launch GitHub Copilot cloud agent sessions directly from within Visual Studio. Previously available in VS Code, cloud agent integration now arrives in Visual Studio, giving developers on both IDEs a consistent way to delegate long-running coding tasks to an autonomous agent.
How Cloud Agent Sessions Work
To start a cloud agent session, developers open the Copilot Chat window, select "Cloud" from the agent picker dropdown in the lower-left corner, and describe the task they want the agent to complete. From that point, GitHub Copilot cloud agent takes over: it creates a GitHub issue to track the work, clones the repository into a GitHub Actions runner, executes the task autonomously, and opens a pull request with the changes when complete.
The key design goal is that developers do not need to stay in the IDE — or even keep their machine on — while the agent works. Visual Studio sends a notification when the pull request is ready, with options to view it inline or open it in a browser. This makes cloud agent sessions well-suited for larger, multi-file refactors, test generation, or documentation tasks that might take minutes or longer to complete.
Prerequisites
Cloud agent integration in Visual Studio requires that the repository be hosted on GitHub and that Copilot has permission to create issues in that repository. The feature is powered by the same GitHub Copilot coding agent infrastructure that runs cloud sessions in VS Code.
Custom User-Level Agents
Alongside cloud agent support, the April update also expands custom agent capabilities. Custom agents — previously scoped to individual repositories via .github/agents/ — can now be defined at the user level, stored in %USERPROFILE%/.github/agents/. These user-level agents travel with the developer across different projects and workspaces, supporting workspace awareness, code understanding, tool access, model selection, and Model Context Protocol (MCP) connections to external knowledge sources.
This means developers can build a personal library of specialized agents that follow them across every project they work on, without needing to configure them repository by repository.
What This Means for Developers
Bringing cloud agent integration to Visual Studio closes the gap between VS Code and the full-featured Visual Studio IDE for Windows developers. Teams working on .NET, C++, and other Windows-centric stacks can now delegate background coding tasks to Copilot without switching editors. Combined with user-level custom agents, the April 2026 update positions Visual Studio as a first-class environment for agentic development workflows.