BYOK GOES FIRST-CLASS: VS CODE OFFLINE + COPILOT MULTI-PROVIDER AND REQUEST HOOKS
Microsoft and GitHub quietly made BYOK and offline LLMs first-class across VS Code, Copilot, and the Copilot SDK. VS Code 1.122’s new air‑gapped mode lets you ...
Microsoft and GitHub quietly made BYOK and offline LLMs first-class across VS Code, Copilot, and the Copilot SDK.
VS Code 1.122’s new air‑gapped mode lets you use chat, tools, and MCP without GitHub sign‑in, enabling fully offline workflows with local models, though inline completions still require extra tooling InfoWorld.
The Copilot CLI update keeps BYOK model selections for custom agents and adds quality‑of‑life improvements like a skills manager and better session persistence v1.0.65. The GitHub app now remembers your last model/reasoning settings, supports quick chat without a repo, and shows custom provider branding like Ollama in the picker (v1.0.7, v1.0.8).
Under the hood, the Copilot SDK adds an experimental multi‑provider BYOK registry and an HTTP/WebSocket request callback so you can intercept, mutate, or route every LLM call for logging, headers, or proxying (v1.0.4, Java v1.0.4).
You can keep prompts and code inside your network while still using Copilot-era workflows.
The SDK’s request hooks and multi-provider registry enable audit, policy, and routing without forking every call site.
-
terminal
Configure VS Code BYOK without GitHub sign‑in and point it at a local model (e.g., Ollama or LM Studio); verify chat/tools and MCP work fully offline.
-
terminal
Use Copilot SDK request callbacks to route through an internal proxy, inject headers, log prompts/latency, and test multi‑provider failover policies.
Legacy codebase integration strategies...
- 01.
Adopt BYOK on air‑gapped dev boxes while keeping Copilot for inline completions; document the gap and provide a fallback path.
- 02.
Enforce data egress and audit by terminating all SDK traffic at an internal gateway via the new request callback; strip PII and add per‑team routing.
Fresh architecture paradigms...
- 01.
Design a multi‑provider registry from day one: pick providers by task (chat vs. code vs. RAG), cost, or data sensitivity.
- 02.
Build team skills and automations with the CLI’s new skills manager; use the app’s quick chat to bootstrap workflows before wiring repos.
Get daily VS-CODE + SDLC updates.
- Practical tactics you can ship tomorrow
- Tooling, workflows, and architecture notes
- One short email each weekday