Skip to content

feat: VS Code + GitHub Copilot Support for MCP Servers and Custom Agents#3457

Open
y0sif wants to merge 6 commits intoadenhq:mainfrom
y0sif:feat/vscode-github-copilot-3299
Open

feat: VS Code + GitHub Copilot Support for MCP Servers and Custom Agents#3457
y0sif wants to merge 6 commits intoadenhq:mainfrom
y0sif:feat/vscode-github-copilot-3299

Conversation

@y0sif
Copy link

@y0sif y0sif commented Feb 3, 2026

Closes #3299

Summary

Add VS Code + GitHub Copilot support for existing MCP servers and custom agents, following the same pattern as the Cursor and Antigravity integrations. Enables developers using VS Code to access the same agent-building capabilities through GitHub Copilot's custom agents feature.

Changes

  • .vscode/mcp.json – MCP server configuration for agent-builder and tools using uv commands with workspace-relative paths
  • .vscode/settings.json – Enable MCP servers and custom agent skills (chat.useAgentSkills, chat.mcp.access, chat.mcp.autostart)
  • .github/agents/ – 6 custom agent files (.agent.md format with YAML frontmatter):
    • agent-workflow.agent.md
    • building-agents-core.agent.md
    • building-agents-construction.agent.md
    • building-agents-patterns.agent.md
    • testing-agent.agent.md
    • setup-credentials.agent.md
  • docs/vscode-copilot-setup.md – Comprehensive setup guide with quick start, troubleshooting, and advanced configuration
  • README.md – VS Code + GitHub Copilot section with usage examples
  • DEVELOPER.md – Updated IDE Skills/Agents section with VS Code instructions and .github/agents/ in project structure

Why .agent.md files instead of symlinks?

VS Code custom agents require a different format than Claude Code skills:

  • Format: YAML frontmatter + Markdown content (not pure Markdown)
  • Location: .github/agents/ (VS Code convention, not .vscode/)
  • Structure: Must include description, name, tools, and target fields
  • Limitations: VS Code doesn't support symlinks for agent discovery

Content is adapted from .claude/skills/ to be concise and VS Code-optimized, maintaining the same functionality.

Key Technical Decisions

  1. uv instead of python: Consistent with project standards for better dependency management and environment isolation
  2. ${workspaceFolder} variables: Ensures portability across different contributor setups

Testing

  • .vscode/mcp.json validates (JSON, proper stdio MCP format)
  • .vscode/settings.json includes only MCP/agent-related settings
  • 6 .agent.md files created with valid YAML frontmatter
  • No changes to core or tools code; config and docs only

Checklist

Related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Coding Agent Integration]: VS Code + GitHub Copilot Support for MCP Servers and Custom Agents

1 participant