microsoft / microsoft/foundry-dev-tools
Remote Ollama models cannot be managed
@QinghuiMeng-M is already working on this.
Since Dec 9, 2025.
- Dominant language
- JavaScript
- Stars
- 2.1k
- Forks
- 260
- Avg merge
- 42m
- Merged PRs (30d)
- 29
Description
Hey All. I have a remote Ollama instance with models that I want to use for copilot chat, inline completion, etc.
It seems that remote Ollama models to not show up in the "Manage Language Models" picker, which would allow me to select them as models to use for chat and other applications. Remote models work perfectly well in the model playground.
Oddly, when I am running a local instance of Ollama, those models do show up in the picker.
In the below image, deepseek-r1:1.5b is running on local Ollama, and deepseek-r1:8b is running on remote Ollama, but only 1.5b is selectable in the "Manage Language Models" picker.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.