Microsoft shipped the August update to Visual Studio 2026 on Aug. 25, and the headline change is not a UI refresh or a new keyboard shortcut. It’s a mechanism that lets organizations publish custom GitHub Copilot agents once and have them appear automatically across every eligible repository in the company.
Org-level agent distribution
Until now, custom agents in Visual Studio were largely a per-project affair. You defined an agent with its own instructions, tools, and purpose for one repo and repeated the process for the next. The August update changes that.
GitHub organization and enterprise owners can now store agent definitions in an org’s .github or .github-private repository. When a developer opens an eligible repo, Visual Studio detects those agents and adds them to the Copilot agent picker automatically. Enterprise-level agents follow the same pattern from a designated governance repository.
GitHub’s documentation describes these as specialized versions of Copilot configured with tailored prompts, tools, and context. Organizations can test agents privately before rolling them out broadly. Enterprise administrators can restrict who is allowed to manage them, and GitHub provides rulesets to protect agent definitions from unauthorized changes.
Custom agents can also connect to external tools and data sources via the Model Context Protocol (MCP), so an agent scoped to a specific task can pull in context a general coding model would not otherwise have.
One important limit: organization-level custom instructions express preferences, not enforced policy. Developers can disable them through Visual Studio’s Copilot settings. These are not a substitute for security controls or compliance systems.

️ Thinking effort controls and cloud handoff
The update also adds a Low / Medium / High thinking-effort setting for supported reasoning models, accessible from the model picker. Low is for quick suggestions; High is for hard algorithms, architecture decisions, or debugging sessions where depth matters more than speed. Microsoft frames this as a way to balance response quality, latency, and token consumption against the difficulty of the task at hand.
Separately, developers can now start a cloud agent session from inside Visual Studio and hand a task off to GitHub Copilot’s coding agent. The agent works remotely toward a pull request while the developer continues locally or closes the IDE entirely. Visual Studio notifies the developer when the pull request is ready.
This follows Microsoft’s Aug. 24 announcement of a Bring Your Own Model preview for Visual Studio, which lets developers connect to a Microsoft Foundry deployment or use credentials from another supported model provider in Agent Mode. Centralized admin controls for BYOM are planned but not yet in the preview.
Git worktrees and submodules
Not everything is AI. Visual Studio now has built-in Git worktree support, letting developers maintain multiple working directories for the same repository without stashing changes or cloning again. Worktrees show up in the Git Repository window and branch pickers. First-class Git submodule support is also included, with automatic detection and controls for common management tasks. Microsoft calls this the first milestone, with more improvements planned.
The operator angle here is straightforward: if your team runs more than a handful of repos, org-level agent distribution cuts the per-project configuration overhead that currently makes standardizing AI tooling across a codebase a manual chore.

