Teams can now share custom agents across repositories instead of configuring the same specialized help one project at a time. GitHub organization and enterprise owners can publish agents for everyone in the organization, helping Copilot follow shared workflows and expectations more consistently. Visual Studio automatically detects organization-level agents when you work in an eligible repository and adds them to the\u00a0agent picker<\/strong>. Hover over an agent to see its description and organization source, or select the definition button to open its definition file. This functionality requires a GitHub organization.<\/p>\n Curious how much of your Copilot plan you have used? Open the context window from the prompt box, then select\u00a0View all Copilot usage<\/strong> to jump to your full plan details. Usage notifications are easier to act on too, so you will know when you are close to your limit and what options you have to keep working. It is a small change that puts useful information closer to the moment you need it.<\/p>\n Ever stashed half-finished work just to investigate another branch?\u00a0Git worktree support<\/a> gives each branch its own working directory, so your current changes stay in place while you switch to another task. In the Git Repository<\/strong> window, right-click a branch and select New Worktree From<\/strong>. You can create the worktree from a new or existing branch, or start from a commit in the history graph. Open it in the current window or a new Visual Studio instance when you want both branches side by side. When the extra working directory is no longer needed, right-click it and select Delete Worktree<\/strong>.<\/p>\n Your worktrees appear alongside branches in the Git Repository<\/strong> window, branch picker, and repository picker.<\/p>\n One of our most requested Git improvements<\/a> is here. Visual Studio now gives submodules a dedicated section in the Git Repository<\/strong> window, better visibility in Git Changes<\/strong>, and a repository picker that clearly shows the parent-child hierarchy. From the Submodules<\/strong> section, you can add, update, and delete submodules. Visual Studio discovers them automatically when you open a solution or folder and keeps them out of the general local repositories list, reducing clutter.<\/p>\n Submodules are read-only by default. To make changes inside them, go to Tools > Options > Source Control > Git<\/strong>, find Automatically activate multiple repositories<\/strong>, and select Yes, include submodules<\/strong>. This is the first milestone for the experience, with more improvements planned.<\/p>\n![\"Thinking](\"https:\/\/devblogs.microsoft.com\/visualstudio\/wp-content\/uploads\/sites\/4\/2026\/08\/vs18.9_model-thinking-effort-thumbnail.webp\")
<\/a><\/p>\nOrganization-level custom agents<\/h3>\n
<\/a><\/p>\nAccess your Copilot usage<\/h3>\n
<\/a><\/p>\nWorktrees: work on multiple branches at once<\/h3>\n
<\/a><\/p>\n<\/a><\/p>\nGit submodule support<\/h3>\n
<\/a><\/p>\n