microsoft / microsoft/copilot-for-eclipse
[Feat] BYOK: Add Gateway provider for custom inference endpoints
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 126
- Forks
- 60
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
The Model Management preference page lists a fixed set of providers (Azure, OpenAI, Anthropic, OpenRouter, Gemini, Groq). There is no way to add a model from a custom inference endpoint, such as an enterprise API gateway or a locally running inference server, because every provider targets a hard-coded upstream host.
Describe the solution you'd like
Add a Gateway entry to the provider list alongside the existing ones. When the user selects Gateway and clicks "Add Model...", a credentials dialog should collect:
- Gateway base URL (e.g. https://my-gateway.internal/v1 or http://localhost:11434)
- API key with show/hide toggle (optional for local servers)
- Auth scheme selector: x-api-key header or Authorization: Bearer
- Model discovery toggle to fetch available models from {baseUrl}/v1/models automatically
The rest of the flow (Remove Model, Enable, Reload, Change API, Delete API) stays exactly as it is for all other providers.
Describe alternatives you've considered
There is no working alternative within the current UI. The existing providers cannot be redirected to a custom endpoint. Configuring an HTTP proxy is the only partial workaround but it adds infrastructure complexity and does not cover local servers on loopback.
Additional context
The screenshot below shows the current provider list. The request is to add Gateway as a seventh entry in the same list, with no changes to the existing provider flows.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Model Management preference page and trace the existing provider list and “Add Model...” credentials flow. Define how Gateway stores its base URL, optional API key, auth scheme, and model-discovery setting, then verify that the existing Remove Model, Enable, Reload, Change API, and Delete API actions remain unchanged and that discovery targets the specified models endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100