Summary
Currently, OpenWiki supports several AI providers, but it does not support GitHub Copilot Models.
It would be valuable to add GitHub Copilot as a first-class AI provider, allowing users to leverage the models already available through their GitHub Copilot subscription without configuring separate API keys.
Motivation
Many developers and enterprise teams are already using GitHub Copilot as their primary AI coding assistant.
GitHub Copilot now provides access to multiple state-of-the-art models (such as OpenAI GPT, Claude, Gemini, etc.), and organizations can centrally manage model availability through GitHub, making it an increasingly common AI platform for development workflows.
Supporting GitHub Copilot would provide several benefits:
Reuse existing GitHub Copilot subscriptions instead of purchasing additional API services
Simplify setup for enterprise users
Reduce API key management
Provide a seamless experience for developers already working inside the GitHub ecosystem
Lower the adoption barrier for OpenWiki
For many enterprise environments, GitHub Copilot has become the standard AI platform, so native support would significantly improve usability.
Proposed Solution
Add a new AI provider named GitHub Copilot.
Possible implementation:
Add GitHub Copilot as a selectable provider in AI settings.
Support authentication through GitHub Copilot.
Use GitHub Copilot's available chat/completions endpoint (or compatible interface) for model inference.
Allow users to choose from the models exposed by their Copilot subscription.
Keep the provider implementation consistent with existing OpenAI/Anthropic provider abstractions.
This could share most of the existing provider interface while only implementing a new authentication layer.
Alternatives Considered
No response
Additional Context
No response
Summary
Currently, OpenWiki supports several AI providers, but it does not support GitHub Copilot Models.
It would be valuable to add GitHub Copilot as a first-class AI provider, allowing users to leverage the models already available through their GitHub Copilot subscription without configuring separate API keys.
Motivation
Many developers and enterprise teams are already using GitHub Copilot as their primary AI coding assistant.
GitHub Copilot now provides access to multiple state-of-the-art models (such as OpenAI GPT, Claude, Gemini, etc.), and organizations can centrally manage model availability through GitHub, making it an increasingly common AI platform for development workflows.
Supporting GitHub Copilot would provide several benefits:
Reuse existing GitHub Copilot subscriptions instead of purchasing additional API services
Simplify setup for enterprise users
Reduce API key management
Provide a seamless experience for developers already working inside the GitHub ecosystem
Lower the adoption barrier for OpenWiki
For many enterprise environments, GitHub Copilot has become the standard AI platform, so native support would significantly improve usability.
Proposed Solution
Add a new AI provider named GitHub Copilot.
Possible implementation:
Add GitHub Copilot as a selectable provider in AI settings.
Support authentication through GitHub Copilot.
Use GitHub Copilot's available chat/completions endpoint (or compatible interface) for model inference.
Allow users to choose from the models exposed by their Copilot subscription.
Keep the provider implementation consistent with existing OpenAI/Anthropic provider abstractions.
This could share most of the existing provider interface while only implementing a new authentication layer.
Alternatives Considered
No response
Additional Context
No response