Microsoft Foundry Local Wires Qwen3.8-27B into GitHub Copilot: Local Coding Agent on ~24 GB VRAM; Vendor Terminal-Bench 2.1 ~73.0
On 2026-11-05 Microsoft Foundry blogged that Foundry Local CLI 0.13.0+ can run 4-bit Qwen3.8-27B (~18 GB weights) on-device via ONNX Runtime and connect it to GitHub Copilot through Bring Your Own Key. Needs an NVIDIA GPU with at least 24 GB VRAM (about 64K context on 24 GB; up to the model's 262K max on 32 GB+). Vendor-cited model-card scores include Terminal-Bench 2.1 73.0 and SWE-bench Pro 61.7; Microsoft also reports higher generation speed than same-quant llama.cpp on RTX 5090 and DGX Spark. Mac and AMD support are still on the roadmap.

Key Takeaways
- Shape: Foundry Local 0.13.0+ runs 4-bit Qwen3.8-27B (~18 GB weights) and connects to the GitHub Copilot app via BYOK
- Hardware: NVIDIA GPU with >=24 GB VRAM; ~64K context on 24 GB, up to 262K on 32 GB+; install CUDA/cuDNN yourself
- Vendor-cited model-card scores (not a 4-bit re-run): Terminal-Bench 2.1 73.0, SWE-bench Pro 61.7, NL2Repo-Bench 42.3, DeepSWE 1.1 42.2
- Stack: ONNX Runtime + DFlash2 speculative decoding + INT4/KV quant + prefix caching; Microsoft says the gap vs llama.cpp widens past 131K tokens
- Limits: Microsoft says cloud models still win on hard reasoning; Mac/AMD not shipped; Copilot CLI local model does not imply offline—set COPILOT_OFFLINE separately
