MicrosoftDocs · learn-build-service-prod · May 15, 2026 · Apr 27, 2026 · May 5, 2026 · May 5, 2026
diff --git a/docs/code-quality/install-roslyn-analyzers.md b/docs/code-quality/install-roslyn-analyzers.md
@@ -1,5 +1,5 @@
 ---
-title: Install external analyzers
+title: Install External Analyzers
 description: Learn how to install external analyzers in Visual Studio. Install analyzers with NuGet analyzer packages and as a VSIX extension.
 author: mikadumont
 ms.author: midumont
@@ -10,7 +10,7 @@ helpviewer_keywords:
 - code analysis, managed code
 - analyzers
 - Roslyn analyzers
-ms.date: 03/25/2024
+ms.date: 05/15/2026
 ---
 
 # Install external analyzers
@@ -52,8 +52,18 @@ To install a Visual Studio Extension-based analyzer, follow these steps:
 
    The **VSIX Installer** dialog box opens.
 
+   ::: moniker range="visualstudio"
+
+   ![Screenshot of VSIX Installer dialog in Visual Studio.](media/visualstudio/installer-code-analysis.png)
+
+   ::: moniker-end
+
+   ::: moniker range="vs-2022"
+
    ![Screenshot that shows the VSIX Installer dialog box.](media/vsix-installer-code-analysis.png)
 
+   ::: moniker-end
+
 1. Select **Modify** to start the installation.
 
 1. After a minute or two, the installation completes. Select **Close**.

diff --git a/docs/code-quality/media/visualstudio/installer-code-analysis.png b/docs/code-quality/media/visualstudio/installer-code-analysis.png
diff --git a/docs/ide/copilot-agent-mode.md b/docs/ide/copilot-agent-mode.md
@@ -1,7 +1,7 @@
 ---
 title: Use Agent Mode
 description: Use the GitHub Copilot agent to iterate on code in Visual Studio by making code edits, running commands, and reading error/build context.
-ms.date: 04/02/2026
+ms.date: 05/11/2026
 ms.update-cycle: 180-days
 ms.topic: get-started
 author: RoseHJM
@@ -128,7 +128,7 @@ Agent mode can use the following tools for responding to a request:
 - [Agent skills](copilot-agent-skills.md) that provide task-specific instructions
 
 > [!TIP]
-> Visual Studio also includes built-in agents like @debug, @profiler, @test, and @vs that integrate with specific IDE features. You can also create custom agents for your team workflows. For more information, see [Use custom agents in GitHub Copilot](copilot-specialized-agents.md).
+> Visual Studio also includes built-in agents like @debug, @profiler, @test, and @vs that integrate with specific IDE features. In agent mode, @debug can guide bug reproduction, instrumentation and telemetry collection, and fix validation. You can also create custom agents for your team workflows. For more information, see [Use custom agents in GitHub Copilot](copilot-specialized-agents.md).
 
 To view and manage the tools that are available in agent mode, select the **Tools** icon in the chat window.
 
@@ -165,8 +165,19 @@ Once you enable the tool, Copilot uses it automatically when answering your ques
 
 Supported languages include C++, C#, Razor, and TypeScript, plus any other language for which you have a supported Language Server Protocol (LSP) extension installed.
 
+For C++ projects, agent mode can also use C++ tools to navigate call and class hierarchies. For more information, see [C++ code editing tools](#c-code-editing-tools).
+
 For best results, write clear prompts and use AI models that support tool-calling. For more information about model capabilities, see [AI model comparison (GitHub Docs)](https://docs.github.com/copilot/reference/ai-models/model-comparison).
 
+### C++ code editing tools
+
+When C++ code editing tools are enabled in the **Tools** list in Copilot Chat, agent mode can use these Visual Studio-specific tools:
+
+- `get_symbol_call_hierarchy` to traverse call hierarchies
+- `get_symbol_class_hierarchy` to navigate class and type hierarchies
+
+These tools help the agent reason over C++ relationships so it can make more precise navigation and editing decisions. To use these tools, install the **Desktop development with C++** workload. After these tools are available and enabled, agent mode uses them automatically when applicable.
+
 :::moniker-end
 
 ## Manage tool approvals

diff --git a/docs/ide/copilot-specialized-agents.md b/docs/ide/copilot-specialized-agents.md
@@ -1,7 +1,7 @@
 ---
 title: Use custom agents in GitHub Copilot
 description: Learn about built-in agents for debugging, profiling, testing, and code modernization, and how to create custom agents for your team workflows.
-ms.date: 04/21/2026
+ms.date: 05/11/2026
 ms.topic: how-to
 author: mikejo5000
 ms.author: mikejo
@@ -43,12 +43,6 @@ You can access custom agents by using **@ syntax**: Type `@` followed by the age
 
 :::moniker-end
 
-:::moniker range="vs-2022"
-
-:::image type="content" source="media/vs-2022/agent-picker.png" alt-text="Screenshot showing the agent picker with custom agents.":::
-
-:::moniker-end
-
 ## Built-in agents
 
 Each built-in agent focuses on a specific developer workflow. These agents integrate with Visual Studio's native tooling in ways that a generic assistant can't.
@@ -68,8 +62,13 @@ Each built-in agent focuses on a specific developer workflow. These agents integ
 | **@profiler** | Connects to Visual Studio's profiling infrastructure to identify bottlenecks and suggest targeted optimizations grounded in your codebase, not generic advice. |
 ::: moniker-end
 
+
 :::moniker range="visualstudio"
 
+## Cloud agents
+
+In Copilot Chat, you can start cloud-based agent sessions from the agent picker. A connected repository means you have a local solution open from a GitHub repository and you're signed in to GitHub in Visual Studio. These remote sessions are powered by the GitHub Copilot coding agent and can create repository issues and pull requests in that repository.
+
 ### Use the @debugger agent
 
 The @debugger agent helps you diagnose errors systematically by analyzing your debugging context. It also supports an end-to-end agentic workflow that reproduces bugs, instruments your app with tracepoints and conditional breakpoints, and validates fixes using live runtime data. For more information, see [Agentic bug resolution with the Debugger Agent](../debugger/debug-with-copilot.md#agentic-bug-resolution-with-the-debugger-agent).
@@ -106,10 +105,6 @@ The @test agent generates unit tests that match your project's testing framework
 
 For more comprehensive .NET testing support, see [GitHub Copilot testing for .NET](../test/github-copilot-test-dotnet-overview.md).
 
-::: moniker-end
-
-:::moniker range="visualstudio"
-
 ### Use the @modernize agent
 
 The @modernize agent helps with framework migrations and dependency upgrades for .NET and C++ projects.
@@ -196,6 +191,15 @@ Tools extend what your custom agent can do. You can specify which tools the agen
 > [!IMPORTANT]
 > Tool names vary across GitHub Copilot platforms. Check the tools available in Visual Studio specifically to make sure your agent works as expected. Select the **Tools** icon in the chat window to see available tool names.
 
+### Language-specific tools for C++
+
+C++ code editing tools are generally available in agent mode. If the C++ workload is installed, your custom agent can use these Visual Studio-specific tool names in its `tools` array:
+
+- `get_symbol_call_hierarchy` for call hierarchy navigation
+- `get_symbol_class_hierarchy` for class and type hierarchy navigation
+
+These tools give agents language-aware navigation for C++ and help improve precision when analyzing and editing C++ code.
+
 ### Connect to external sources with MCP
 
 By using [MCP servers](mcp-servers.md), your custom agents can access external knowledge sources such as:

diff --git a/docs/ide/default-keyboard-shortcuts-in-visual-studio.md b/docs/ide/default-keyboard-shortcuts-in-visual-studio.md
@@ -1,7 +1,7 @@
 ---
 title: Keyboard shortcuts
 description: Learn about the default keyboard shortcuts in Visual Studio that allow you to access a variety of commands and windows.
-ms.date: 3/26/2026
+ms.date: 04/27/2026
 ms.topic: reference
 helpviewer_keywords:
 - shortcut keys [Visual Studio], keyboard binding schemes
@@ -11,6 +11,7 @@ helpviewer_keywords:
 - keyboard shortcuts
 author: ghogen
 ms.author: ghogen
+ms.custom: awp-ai
 
 ms.subservice: general-ide
 ---
@@ -523,6 +524,9 @@ These keyboard shortcuts are *global*, which means that you can use them when an
 |Go to web access|**Ctrl+0** (zero), **Ctrl+A**<br /><br /> or<br /><br /> **Ctrl+0, A**| TeamFoundationContextMenus.Commands.GoToWebAccess |
 |Go to work items|**Ctrl+0** (zero), **Ctrl+W**<br /><br /> or<br /><br /> **Ctrl+0, W**| TeamFoundationContextMenus.Commands.GoToWorkItems |
 
+> [!NOTE]
+> The legacy Team Explorer work items experience is deprecated. Going forward, the **Go to work items** command no longer opens inside Visual Studio and instead opens work items in the web portal, where you'll find a modern, more consistent experience. This change aligns with updates introduced in Visual Studio 2019 and 2022 and ensures that all work item features are available through the web experience. For more information, see [work items in Visual Studio](https://devblogs.microsoft.com/devops/work-items-in-visual-studio/).
+
 ### <a name="bkmk_test-global-shortcuts"></a> Test: global shortcuts
 
 |Commands|Keyboard shortcuts|Command ID|

diff --git a/docs/ide/develop-code-in-visual-studio-without-projects-or-solutions.md b/docs/ide/develop-code-in-visual-studio-without-projects-or-solutions.md
@@ -1,14 +1,15 @@
 ---
 title: Develop code without projects or solutions
 description: Develop code directly in Visual Studio without placing the code in a solution or project, and start working quickly with IntelliSense, search, debugging, and more. 
-ms.date: 11/7/2023
+ms.date: 04/27/2026
 ms.topic: how-to
 helpviewer_keywords:
 - open folder [Visual Studio]
 - anycode [Visual Studio]
 - projects and solutions, develop code without
 author: Mikejo5000
 ms.author: mikejo
+ms.custom: awp-ai
 
 ms.subservice: general-ide
 ---
@@ -83,6 +84,9 @@ As of Visual Studio 2019 [version 16.8](/visualstudio/releases/2019/release-note
 
 You can still use Team Explorer in Visual Studio 2022 and in Visual Studio 2019 [version 16.8](/visualstudio/releases/2019/release-notes/) and later. However, you might find it easier to use the new Git experience. For more information, see [How Visual Studio makes version control easy with Git](../version-control/git-with-visual-studio.md).
 
+> [!NOTE]
+> The legacy work items experience in Team Explorer is deprecated. Going forward, work items no longer open inside Visual Studio and instead open in the web portal, where you'll find a modern, more consistent experience. This change aligns with updates introduced in Visual Studio 2019 and 2022 and ensures that all work item features are available through the web experience. For more information, see [work items in Visual Studio](https://devblogs.microsoft.com/devops/work-items-in-visual-studio/).
+
 1. In Visual Studio, choose the **Team Explorer** tab to open **Team Explorer**. If you don't see the tab, open it from **View** > **Team Explorer**.
 
 1. In Team Explorer, under the **Local Git Repositories** section, choose the **Clone** command and then paste the URL of the GitHub page into the text box.

diff --git a/...alstudio/account-settings-filter-account-dialogs-tenants-filtered-out-state.png b/...alstudio/account-settings-filter-account-dialogs-tenants-filtered-out-state.png
diff --git a/docs/ide/media/visualstudio/add-personalization-account.png b/docs/ide/media/visualstudio/add-personalization-account.png
diff --git a/docs/ide/media/visualstudio/apply-filter.png b/docs/ide/media/visualstudio/apply-filter.png
diff --git a/docs/ide/media/visualstudio/reauthenticate-account.png b/docs/ide/media/visualstudio/reauthenticate-account.png
diff --git a/docs/ide/media/visualstudio/select-system-web-browser.png b/docs/ide/media/visualstudio/select-system-web-browser.png
diff --git a/docs/ide/media/visualstudio/windows-authentication-broker.png b/docs/ide/media/visualstudio/windows-authentication-broker.png
diff --git a/docs/ide/visual-studio-github-copilot-get-started.md b/docs/ide/visual-studio-github-copilot-get-started.md
@@ -1,7 +1,7 @@
 ---
 title: Get Started with GitHub Copilot
 description: Learn how to get started with GitHub Copilot in Visual Studio.
-ms.date: 2/18/2026
+ms.date: 05/11/2026
 ms.update-cycle: 180-days
 ms.topic: get-started
 author: RoseHJM
@@ -56,10 +56,12 @@ Copilot is now ready to use in Visual Studio.
 After you sign in, use Copilot in the chat window and throughout the IDE.
 
 - **Use [agent mode](copilot-agent-mode.md) and [MCP servers](mcp-servers.md)**: In the chat window, select **Ask** and switch to **Agent** to enable agent mode. Use the tools icon to access Model Context Protocol (MCP) servers, configure servers, and choose which tools Copilot can use. For example, to get Copilot assistance with generating targeted code, send "Write unit tests for the methods in this file."
+  - As part of agent mode workflows, Copilot Chat can connect to cloud agents to run remote coding sessions that create repository issues and pull requests in your connected GitHub repository. You might be prompted to grant repository permissions the first time you start a cloud session, or when more permissions are required.
 
-- **Use [completions](visual-studio-github-copilot-extension.md) and [next edit suggestions](copilot-next-edit-suggestions.md)**: As you code, Copilot provides suggestions directly in the editor. Copilot suggests both new code (shown as gray text) and edits to existing code.
+- **Use [completions](visual-studio-github-copilot-extension.md) and [next edit suggestions](copilot-next-edit-suggestions.md)**: As you code, Copilot provides suggestions directly in the editor. Copilot suggests both new code (shown as gray text) and edits to existing code. By default, Visual Studio prioritizes IntelliSense over Copilot inline completions. You can customize keyboard shortcuts for accepting Copilot suggestions (full suggestion, next word, and next line) in **Tools** > **Options** > **Environment** > **Keyboard**.
 
 - **Use Copilot actions across Visual Studio**: Find Copilot-powered actions and suggestions on the editor context menu, error list, feature search, and other areas of the IDE.
+  - Use the Debugger Agent workflow from Copilot Chat or issue context. Start from a GitHub or Azure DevOps issue (or a natural-language prompt) to reproduce a problem, generate hypotheses, add instrumentation, analyze telemetry, and apply targeted fixes while validating live runtime behavior.
 
 ## Tailor Copilot chat to your workflow
 
@@ -71,6 +73,8 @@ Customize Copilot for your project and your development workflow.
 
 - **Add custom instructions**: Add reusable [custom instructions](copilot-chat-context.md#use-custom-instructions) in `.github/copilot-instructions.md` and [prompt files](copilot-chat-context.md#use-prompt-files) in `.github/prompts` to customize Copilot responses for your coding style or project needs.
 
+- **Create and manage custom agents**: In the Copilot Chat window, use the agent picker at the top of the prompt area to create and select custom agents. User-level custom agent definitions are stored in `%USERPROFILE%\.github\agents`. These agents retain workspace awareness, tool configuration, model selection, and MCP connections. For more information, see [Use built-in and custom agents with GitHub Copilot](copilot-specialized-agents.md).
+
 ## Helpful resources
 
 To review Copilot features at any time, select **GitHub Copilot Walkthrough** from the **GitHub Copilot** badge in the upper-right corner of Visual Studio.
@@ -81,4 +85,4 @@ Try building a complete app with the [Hands-on lab: GitHub Copilot in Visual Stu
 
 - [GitHub Copilot Trust Center: Learn about security, privacy, compliance, and transparency](https://copilot.github.trust.page)
 - [Completions](visual-studio-github-copilot-extension.md)
-- [Chat](visual-studio-github-copilot-chat.md)
+- [Chat](visual-studio-github-copilot-chat.md)