💬 Feedback wanted: Custom agents in GitHub Copilot (partner-built & community-built)

[ebndev]

We announced custom agents for GitHub Copilot at GitHub Universe, and now we’re launching a growing collection of partner-built agents for observability, IaC, security, databases, incident response, experimentation, automation, and more. These agents are designed to help you run real engineering workflows in your terminal, in VS Code, or on github.com — not just generate code.
This Discussion is your space to try them, break them, and tell us what’s missing. You can also learn more in our blog with a guide to get started and a full readout of our current custom agents from our partners.

🧩 What custom agents are

Custom agents are Markdown-defined domain experts that extend the Copilot coding agent. They're lightweight, zero-infrastructure, and can run wherever Copilot runs:

• Terminal (Copilot CLI)
• VS Code (Copilot Chat)
• github.com (Copilot panel to Agents)

They help developers automate real workflows: scanning dependencies, optimizing Terraform, responding to incidents, generating release notes, tuning databases, implementing feature flags, and more.

🔌 Partner-built custom agents available today

These agents are built with GitHub partners and ready to drop into any repository (and you can find all of them here):

Observability

• Dynatrace Observability & Security Expert
• Elasticsearch Remediation Agent

Security

• JFrog Security Agent
• StackHawk Security Onboarding

Databases

• MongoDB Performance Advisor
• Neon Migration Specialist
• Neon Performance Analyzer
• Neo4j Docker Client Generator

DevOps & IaC

• Terraform Infrastructure Agent
• Arm Migration Agent
• Octopus Release Notes Expert
• DiffBlue Java Unit Test Agent

Incidents & Project Management

• PagerDuty Incident Responder
• Monday Bug Context Fixer

Feature Flags & Experimentation

• LaunchDarkly Flag Cleanup
• Amplitude Experiment Implementation

Automation & APIs

• Apify Integration Expert
• Lingo.dev Internationalization Implementation
• Factory.ai Code Spec Agent
• You can see the exact agent files and examples in the awesome-copilot repo.

▶️ Try an agent in under 60 seconds

Just drop a file in your repository:
.github/agents/<agent>.agent.md

And run it from Copilot CLI:
copilot --agent=<agent> --prompt "<your task>"

Or select it in VS Code Copilot Chat or github.com via Copilot panel and Agents.

📣 How you can help

Please comment below with:

• Agents you tried
• Your workflow and environment
• What worked well
• What didn’t
• Screenshots or prompts that illustrate the behavior
• Agents you want us to build next

🙏 Thank you

Your feedback directly shapes how we extend Copilot beyond code generation into real, end-to-end engineering workflows. We can’t wait to hear what you build.

[wenytang-ms]

Hi Team, the custom agent is really a fantastic design, I'm also working on such scenario for vscode java debug. The debug agent is implemented in the VS Code extension using LanguageModelTool. The agent calls tools as needed. whenever this agent is enabled, the default VS Code LanguageModelTool is not active by default. Should the design allow LanguageModelTool to be enabled by default?