GitHub Copilot adds bring-your-own keys across Free, Pro, Business, and Enterprise

• pierceboggan's launch post says bring-your-own keys in VS Code now works across every Copilot plan, including Free, Pro, Pro+, Business, and Enterprise.
• VS Code's announcement frames it as a way to plug in a different language model or API key, while the BYOK page points to setup details for managed plans.
• pierceboggan explicitly called out local providers such as LM Studio and cloud providers such as OpenRouter, which keeps Copilot's agent harness in front of third-party backends.
• the GitHub changelog retweet adds two enterprise-facing details: Business and Enterprise users can supply provider API keys, and admins can control which models are available.
• pierceboggan's follow-up also teased an upcoming /remote command for VS Code, separate from the BYOK rollout.

You can jump straight to the VS Code 1.117 update, open the BYOK setup page, and watch VS Code's short demo show the key-paste flow inside settings. pierceboggan's post is also unusually direct about the real pitch: keep the Copilot harness, swap the model backend.

The headline change is scope. BYOK is not limited to enterprise tenants or a preview tier anymore, according to pierceboggan's launch post; it spans Free, Pro, Pro+, Business, and Enterprise.

That makes this feel less like an admin feature and more like a routing layer inside VS Code. The official release notes live in the VS Code 1.117 update, and the VS Code account pitches the feature as plain model choice: use a different model than the default one already wired into Copilot.

The most concrete architecture clue comes from pierceboggan's wording: developers can use local providers like LM Studio or cloud providers like OpenRouter. That implies Copilot's chat and agent UX can sit on top of provider APIs you already use elsewhere.

The rollout breaks down into a few mechanics:

• Bring your own API key into Copilot's VS Code flow, per the official announcement.
• Route requests to local model servers such as LM Studio, per pierceboggan's example.
• Route requests to hosted aggregators such as OpenRouter, also per the same launch post.
• Apply admin controls over model availability for managed seats, according to the changelog summary.

the demo clip shows the UX is lightweight: open settings, paste a key, and continue inside the existing Copilot interface rather than swapping extensions.

The managed-plan wrinkle is model governance. The changelog summary says Business and Enterprise users can bring provider keys into VS Code, and that administrators can decide which models are exposed to their users.

That is a different promise from simple hobbyist BYOK. Free and Pro expand experimentation, while the managed tiers add a policy surface on top of third-party providers. The setup docs are linked from VS Code's announcement through the BYOK page.

One more thing slipped out in the thread: pierceboggan said /remote is coming to VS Code, with more polish work still underway before a broader rollout.

There is no public feature breakdown in the evidence here, but it is a separate product breadcrumb attached to the BYOK launch, not part of the key-routing feature itself.