GitHub Copilot in Visual Studio Adds Organization-Wide Custom Agents
GitHub CopilotGitHub organization and enterprise owners can now publish custom agents that are automatically detected across every repository in their organization inside Visual Studio, rather than requiring each repository to define its own. The shared agents are stored in the /agents directory of the organization's .github or .github-private repository and appear in Visual Studio's agent picker with their description and organization source, letting teams standardize how Copilot approaches specialized work across many projects at once.
Key Takeaways
- GitHub organization and enterprise owners can now publish custom agents that apply across every repository in the organization, not just one repo at a time.
- Shared agents live in the
/agentsdirectory of the organization's.githubor.github-privaterepository. - Visual Studio automatically detects org-level agents and shows their description and organization source directly in the agent picker.
- Access to a shared agent doesn't require direct access to the repository storing its definition — any org member can use it.
- The feature builds on Visual Studio's existing
.agent.md-based custom agents, extending them from per-repository to organization-wide scope. - It's aimed at platform and DevEx teams that want consistent Copilot behavior across many projects without manual per-repo configuration.
From Per-Repository to Org-Wide Custom Agents
Visual Studio has supported custom agents — specialized versions of Copilot tailored to a team's workflows and coding conventions, defined as .agent.md files — since earlier in 2026, but until now those agents lived at the repository level. GitHub's August update to Copilot in Visual Studio extends custom agents to the organization level, letting a single definition reach every repository a team works in.
How It Works
Organization and enterprise owners can publish custom agents to the /agents directory of their organization's .github or .github-private repository. Visual Studio automatically detects these org-level agents when a developer works inside any repository belonging to that organization, and lists them in the agent picker alongside repository-specific agents, showing both a description and the organization they came from. Because the agents live in a shared organization repository rather than each individual project, they're available to every member of the organization regardless of whether that member has direct access to the source repository storing the agent definitions.
Why It Matters
Teams that had already built useful custom agents previously faced a choice: copy the same .agent.md file into every repository that needed it, or accept inconsistent Copilot behavior across projects. Organization-level custom agents remove that tradeoff, letting platform or DevEx teams define a shared set of specialized agents — for example, one tuned to a company's testing conventions, another for its deployment process — and have them show up automatically everywhere in the organization, without per-repository setup.
Availability
Organization-level custom agents require a GitHub organization and are available now as part of Visual Studio's Copilot integration.