Microsoft has shown how to plug a locally run AI model into GitHub Copilot, so your code never has to leave your PC. In a Foundry blog post dated 5 November 2026, Microsoft says its Foundry Local runtime can now run Qwen3.8-27B, a 27-billion-parameter open coding model, and serve it to GitHub Copilot through Copilot's Bring Your Own Key (BYOK) feature.
Forge PC has not tested this setup. The details below come from Microsoft's Foundry blog and GitHub's documentation, with UK graphics card prices from SpecPrice checked on 15 November 2026.
What Microsoft announced
According to Microsoft, Foundry Local optimises the whole Qwen3.8-27B pipeline on NVIDIA GPUs. The post lists several techniques, including speculative decoding with a small "drafter" model, 4-bit (INT4) weights, a quantised KV cache and CPU offloading.
The key numbers from the blog:
With 4-bit quantisation the model is about 18GB, which Microsoft says makes it runnable on consumer GPUs with 24GB of VRAM, with context windows of up to 64K tokens.
GPUs with 32GB or more can use longer contexts, up to the model's maximum of 262K tokens.
You need Foundry Local CLI 0.13.0 or later, plus NVIDIA's CUDA and cuDNN runtimes, which Foundry Local does not install for you.
Microsoft also compared Foundry Local with llama.cpp running the same 4-bit model on an RTX 5090 and on an NVIDIA DGX Spark, using real GitHub issues. It says Foundry Local delivered higher generation speed at every prompt length it tested, with the gap widening beyond 131K tokens. That is Microsoft's own test, not an independent result.
How it works with GitHub Copilot
Microsoft's walkthrough uses the GitHub Copilot app:
Install Foundry Local with winget install Microsoft.FoundryLocal and check the version.
Load the model with foundry model load qwen3.8-27b. This downloads it the first time and returns a local API endpoint.
In the GitHub Copilot app, open Settings, then Model providers, choose Add provider and select Foundry Local.
Paste the endpoint into the Base URL field, find Qwen3.8-27B in the catalogue and add it.
Switch the model picker to Foundry Local and Qwen3.8-27B.
Microsoft is upfront about the limits. It says local models "may have limited reasoning capabilities compared with advanced cloud models due to their smaller size", and suggests using cloud models for complex tasks and the local model for everyday coding.
The hardware catch for UK buyers
The 24GB VRAM requirement is the real story for most readers. Microsoft's instructions are for NVIDIA GPUs only for now; the company says it plans to add Macs and AMD GPUs later.
In the UK, 24GB and 32GB cards are scarce and expensive. On 15 November 2026, SpecPrice found no stock-checked new listing for any 24GB desktop card at the UK shops it tracks, and its cheapest RTX 3090 was about £2,140 at PcNova, from a feed it could not stock-check. The cheapest in-stock RTX 5090 (32GB) was about £7,000 at Scan. Our guide to the best GPUs for local AI and our advice on buying a used GPU for local AI explain the cheaper routes, and why VRAM matters more than almost anything else.
If you have a smaller card, there are other ways to get a local coding assistant. Qwen3.8-27B is also listed in Ollama's library at 18GB, as we noted in our vision models guide, and you can pair Ollama with VS Code using Continue or the terminal tool Aider, with smaller models that fit your VRAM.
Our verdict
Foundry Local's GitHub Copilot integration is a genuinely useful option if you already own an NVIDIA card with 24GB or more: Microsoft says the 4-bit Qwen3.8-27B model is about 18GB and supports up to 64K tokens of context on 24GB cards. Its speed claims are Microsoft's own, and the company admits local models trail cloud models on harder reasoning. For most UK buyers, the 24GB requirement is the stumbling block, because those cards cost thousands of pounds on 15 November 2026. Forge PC has not tested this setup. New to Foundry Local? Start with our Foundry Local setup guide.