Feature Request: Support Third-Party API Configuration in GitHub Copilot

[achaozuiq]

Feature Request: Support Third-Party API Configuration in GitHub Copilot

Summary

I propose that GitHub Copilot in VSCode should support user-configurable third-party API endpoints, allowing developers to use alternative language models (e.g., Mimo, DeepSeek, Ollama local models) alongside the official Copilot models.

---

Problem Statement

Currently, GitHub Copilot only supports models provided by GitHub/OpenAI. Users cannot configure their own API endpoints, which creates several limitations:

Limitation	Impact
Restricted Model Choice	Users cannot use other high-quality models (e.g., Mimo V2.5 Pro, DeepSeek V4, local Ollama models)
Cost Opacity	Users cannot choose more cost-effective API providers
Privacy Concerns	Sensitive code must be sent to GitHub servers
Network Restrictions	Some regions cannot directly access GitHub API
No BYOK Option	Users with existing API keys from other providers cannot utilize them

---

Proposed Solution

Option A: Settings Configuration (Recommended)

Add a new configuration option in VSCode settings:

{
  "github.copilot.customModels": [
    {
      "id": "mimo-v2.5-pro",
      "name": "Mimo V2.5 Pro",
      "vendor": "mimo",
      "baseUrl": "https://api.example.com/v1",
      "apiKey": "${env:MY_API_KEY}",
      "model": "mimo-v2.5-pro",
      "capabilities": {
        "chat": true,
        "completions": true,
        "maxTokens": 8192,
        "maxInputTokens": 200000
      }
    }
  ]
}

Option B: Enhanced Language Model API

Leverage and extend the existing proposed API (vscode.lm):

// Allow extensions to register custom model providers
vscode.lm.registerLanguageModelChatProvider('custom-provider', {
  provideLanguageModelChat() {
    return {
      id: 'custom-model',
      name: 'Custom Model',
      vendor: 'custom',
      // ... model configuration
    };
  }
});

Option C: Hybrid Mode

• Retain official Copilot models
• Add support for user-configured third-party APIs
• Allow switching via UI dropdown

---

Use Cases

1. Enterprise Users: Companies with private LLM deployments need to route Copilot requests through their own infrastructure
2. Cost Optimization: Users can choose cheaper API providers for non-critical tasks
3. Privacy Compliance: Sensitive code stays within company networks
4. Regional Accessibility: Users in restricted regions can use alternative API endpoints
5. Model Diversity: Developers can leverage specialized models for specific tasks

---

Technical Feasibility

VSCode already has the foundational APIs:

API	Status	Description
vscode.lm.selectChatModels()	Proposed	Select available language models
vscode.lm.sendRequest()	Proposed	Send requests to language models
languageModelChatProviders	Proposed	Extensions can register model providers

The Mimo for Copilot extension already demonstrates this is possible using the proposed API. The infrastructure exists; it just needs official support in the Copilot extension.

---

Expected Benefits

Benefit	Description
Increased User Satisfaction	Users can freely choose their preferred models
Ecosystem Growth	Attracts more API providers to integrate
Competitive Advantage	Matches features of Cursor, Windsurf, and other AI-powered editors
Community Contribution	Developers can contribute extensions and tools
Enterprise Adoption	Enterprises can deploy Copilot with their private models

---

Existing Implementations

Several third-party extensions have successfully implemented this pattern:

Extension	Approach
Mimo for Copilot	Uses proposed languageModelChatProviders API
Continue.dev	Standalone extension with multi-API support
Cline / Roo Code	Standalone extension with OpenAI-compatible API support

This demonstrates both the demand and technical feasibility.

---

Comparison with Competitors

Editor	Third-Party API Support
VSCode + Copilot	❌ Not supported
Cursor	✅ Supports custom models
Windsurf	✅ Supports custom models
Zed	✅ Supports custom models

Adding this feature would bring VSCode to parity with competing editors.

---

Conclusion

Supporting third-party API configuration in GitHub Copilot would:

1. ✅ Enhance user experience and choice
2. ✅ Strengthen VSCode's competitive position
3. ✅ Foster ecosystem development
4. ✅ Meet community demand
5. ✅ Enable enterprise adoption

This is a win-win proposal that benefits users, developers, and the VSCode ecosystem.

---

Additional Context

• VSCode is open-source (MIT License)
• GitHub Copilot is a closed-source extension
• The community has been requesting this feature
• Technical infrastructure already exists via proposed APIs

---

Thank you for considering this proposal.

---

Submitted by: A developer passionate about the VSCode ecosystem
Date: 2026-06-26

[vritant24]

We currently support this. You can learn about it here
https://code.visualstudio.com/blogs/2026/06/18/byok-vscode