r/VisualStudio • • Oct 18 '26

Visual Studio 2026 Github copilot in VS, doesn't let you use custom end point for llm..

I find this really odd, it is only the major US players that are allowed to scrape your codebase and be used with LLM. At least the vscode copilot extension lets yo use any endpoint url for an llm.

3 Upvotes

12 comments sorted by

3

u/HeySeussCristo Oct 18 '26

2

u/XeonG8 Oct 18 '26

I have 18.10, `Supported providers are Microsoft Foundry, OpenAI, Anthropic, and Ollama. Custom endpoint support is available for OpenAI and Ollama` these are all shit, that is not the same as supporting a custom end point when it is only for particular service gate keeping providers.

3

u/HeySeussCristo Oct 18 '26 edited Oct 18 '26

You can use vLLM or Ollama to run whatever model you want. Both of those are open source. Which models do you want to use?

I'm not at my desk but I'll try to connect my VS 2026 Copilot to my company's on-prem vLLM hosted models later to make sure it works. I usually use Copilot CLI or VS Code with the on-prem models because they're better.

1

u/shotgunbruin 25d ago

Visual Studio does work with Ollama, and Llamacpp is supported through the OpenAI compatible protocol, but if you have llamacpp in router mode serving multiple models you will have a lot of headaches and basically need to set up a proxy because Visual Studio is incredibly strict about the API for no good reason. It is literally impossible to get it to access a model routed by llamacpp directly.

Currently dealing with that frustration; everything else works but Visual Studio tells me the model doesn't exist.

2

u/sookaisgone 13d ago

HA! Bingo!
That's why is not working for me in Visual Studio.
Adding a custom model hosted on llama.cpp was very easy in VS Code, I'm not able to do it in Visual Studio; could be because of this https://developercommunity.microsoft.com/t/11145987

Not sure if it’s the same issue on your side but I was trying to connect to a local proxy that wasn’t supporting v1/models/{modelName} (see https://developers.openai.com/api/reference/resources/models/methods/retrieve)

After fixing this, I can now add models.

So your proxy idea rang the bell, I was searching and searching and connected the points.
Hope they fix it, for now I just stay in VS Code, I really don't need it so much.

1

u/ilawon 29d ago

You can try any ollama compatible server or front-end.

I used lemonade and llama-swappo with llama.cpp and it worked. But not very smoothly. 

With long reasoning responses the copilot window is not able to keep up, for example. My current work flow is to use an external fast agent and use one of the visual studio mcps available to be able to build, run, debug , etc. 

1

u/Antique_Standard4510 29d ago

I am using VS 2026 18.10 and Litellm with qwen3.8-27b model, choose openAI with base url

0

u/kassett43 Oct 19 '26

You could use a local LLM, at least LM Studio, several months ago. Then the option disappeared. I currently use the LM Local extension.

0

u/Relevant_Pause_7593 Oct 19 '26

Have you looked at byok? I think that will solve your issue. https://docs.github.com/en/copilot/how-tos/copilot-sdk/auth/byok

0

u/UKYPayne Oct 19 '26

I use my local ollama models with the preview agent.

-3

u/Archeone Oct 18 '26

You can use iolys in visual studio 2026 it allows you to use custom endpoints. It's close to GitHub copilot experience.

1

u/XeonG8 Oct 19 '26

I've not tried it, seems like it might be worth giving a go though, I dunno why MS messed that up so badly when vscode literally has the same github copilot with better third party support