Merge pull request #15279 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-21 16:00 UTC

Author: learn-build-service-prod[bot]

docs/debugger/includes/remote-debugger-requirements.md

@@ -15,36 +15,20 @@ translation.priority.ht:
   - "zh-cn"
   - "zh-tw"
 ---
-### Supported Operating Systems  
+### System requirements
 
-The remote computer must be running one of the following operating systems: 
+The remote tools support the same system requirements as Visual Studio, with some changes. For details, see the system requirements for your version of Visual Studio:
 
-- Windows 11
-  
-- Windows 10 (not phone)
-  
-- Windows 8 or 8.1 (not phone)
-  
-- Windows 7 Service Pack 1  
+::: moniker range=">=visualstudio"
+- [Remote Tools for Visual Studio 2026 system requirements](/visualstudio/releases/2026/vs-system-requirements#remote-tools-for-visual-studio-system-requirements)
+- [Remote Tools for Visual Studio 2022 system requirements](/visualstudio/releases/2022/system-requirements#remote-tools-and-intellitrace-standalone-collector-for-visual-studio-2022-system-requirements)
+- [Remote Tools for Visual Studio 2019 system requirements](/visualstudio/releases/2019/system-requirements#remote-tools-performance-tools-and-intellitrace-standalone-collector-for-visual-studio-2019-system-requirements)
+::: moniker-end
+::: moniker range="vs-2022"
+- [Remote Tools for Visual Studio 2022 system requirements](/visualstudio/releases/2022/system-requirements#remote-tools-and-intellitrace-standalone-collector-for-visual-studio-2022-system-requirements)
+- [Remote Tools for Visual Studio 2019 system requirements](/visualstudio/releases/2019/system-requirements#remote-tools-performance-tools-and-intellitrace-standalone-collector-for-visual-studio-2019-system-requirements)
+::: moniker-end
 
-- Windows Server 2016
-  
-- Windows Server 2012 or Windows Server 2012 R2  
-  
-- Windows Server 2008 Service Pack 2, Windows Server 2008 R2 Service Pack 1
-  
-### Supported Hardware Configurations  
-  
-- 1.6 GHz or faster processor  
-  
-- 1 GB of RAM (1.5 GB if running on a virtual machine)  
-  
-- 1 GB of available hard disk space  
-  
-- 5400-RPM hard drive  
-  
-- DirectX 9-capable video card running at 1024 x 768 or higher display resolution  
-  
-### Network configuration  
+### Network configuration
 
 The remote computer and the Visual Studio computer must be connected over a network, workgroup, or homegroup, or else connected directly through an Ethernet cable. Debugging between two computers connected through a proxy isn't supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions isn't recommended and may fail or be unacceptably slow.

docs/debugger/remote-debugging.md

@@ -1,7 +1,7 @@
 ---
 title: Remote debugging
 description: Debug a Visual Studio application that has been deployed on a different computer by using the Visual Studio remote debugger.
-ms.date: 12/17/2025
+ms.date: 04/20/2026
 ms.topic: how-to
 f1_keywords:
   - "vs.debug.remote.overview"

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: 2/24/2026
+ms.date: 04/02/2026
 ms.update-cycle: 180-days
 ms.topic: get-started
 author: anandmeg
@@ -147,6 +147,27 @@ Based on the outcome of a tool, Copilot might invoke other tools to accomplish t
 
 Additional tools that you add by running MCP servers aren't automatically enabled. Their checkboxes are cleared by default, and you must select them to activate the tools.
 
+:::moniker range="visualstudio"
+
+### find_symbol tool
+
+The **find_symbol** tool brings language-aware symbol navigation directly to agent mode. When enabled, Copilot automatically uses **find_symbol** to:
+
+- Find all references to symbols across your project
+- Access metadata like type information, declarations, and scope
+
+:::image type="content" source="media/visualstudio/copilot-agent-mode/find-symbol.png" alt-text="Screenshot that shows the find_symbol tool selected in the Copilot Chat pane." lightbox="media/visualstudio/copilot-agent-mode/find-symbol.png":::
+
+Once you enable the tool, Copilot uses it automatically when answering your questions or suggesting code changes.
+
+:::image type="content" source="media/visualstudio/copilot-agent-mode/find-symbol-example.png" alt-text="Screenshot that shows Copilot using the find_symbol tool to analyze and modify code across multiple files." lightbox="media/visualstudio/copilot-agent-mode/find-symbol-example.png":::
+
+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 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).
+
+:::moniker-end
+
 ## Manage tool approvals
 
 When Copilot invokes a tool, it requests confirmation to run the tool. The reason is that tools might run locally on your machine and perform actions that modify files or data.

docs/ide/how-to-report-a-problem-with-visual-studio.md

@@ -22,7 +22,11 @@ Here are the steps to report a problem.
 
     ![Screenshot showing the feedback icon selected in the upper right corner of the Visual Studio Installer and Report a Problem selected on the context menu.](./media/report-a-problem-selected.png)
 
-1. Selecting **Report a Problem** will open [Developer Community](https://developercommunity.microsoft.com/VisualStudio) in your default browser and sign you in using the same account you're signed in to Visual Studio with.
+1. Selecting **Report a Problem** will open [Developer Community](https://developercommunity.microsoft.com/VisualStudio) in your default browser. When prompted, select **Allow** in the browser pop‑up to enable Visual Studio and Developer Community to share sign‑in information.
+
+   ![Screenshot of the browser pop-up prompting you to allow Developer Community to access other apps and services.](media/visualstudio/devcom-sign-in-pop-up.png)
+
+   Once permission is granted, you'll automatically sign-in to Developer Community using the same account info as Visual Studio.
 
    Note: If you are using an ad-blocker you may experience issues during sign-in. Disable the ad-blocker and try to sign in again.