19. November 2026 13 min read
Visual Studio Code chat tab now defaults to Copilot and BYOK is broken
I have been running the Visual Studio Code chat tab with my own models for quite some time now with OpenRouter.ai api key. All of that was quietly working in what Microsoft officially calls the Local harness, which for the rest of us is simply the chat tab that runs inside VS Code itself. Then the October release (1.142) started every new chat in the Copilot harness by default and on 18th of November Microsoft published a blog post that makes it official: the Local chat is deprecated and will be removed in February 2027. I am very disappointed, and not only because my workflow broke over night.
What actually changed
The Copilot chat does not run inside VS Code any more. It runs in a separate Agent Host process, powered by the Copilot SDK, which is the same engine that drives the Copilot CLI and the standalone GitHub Copilot app. Microsoft's reasoning is that one shared runtime lets them ship improvements to all of their products at once, and their own rollout analysis found 14.2% fewer tokens per device. Which is a polite way of saying that it is cheaper for them. For me the first visible change was that the chat tab opened a Copilot session with a model picker full of Copilot models, and my local models were nowhere to be found. The chat participants API that extensions used to plug into the chat is deprecated and only kept alive for Local sessions. Prompt files have to be converted to skills, hooks have to be reviewed by hand and MCP servers have to be configured again, because secrets stored in the editor do not transfer to the new runtime. In other words, everything you have built around the chat tab in the last two years is now legacy.
BYOK in the Copilot chat does not work
Bring your own key (BYOK) is the whole reason I use the chat tab at all. The official documentation marks BYOK in the Copilot chat as experimental, hidden behind the chat.agentHost.byokModels.enabled setting. On my machine experimental is a generous word: the BYOK part of the Copilot interface does not work at all. Pick your own model, send a prompt, and the only thing that comes back is an openssl error. The very same key and the very same endpoint answer within a second in the Local chat. And if you work over SSH, in WSL or in a Dev Container you do not even get that far, because BYOK models are simply not supported in remote Copilot sessions. The error message tells you to switch to the local agent harness to use your own models. That would be the one Microsoft is deleting in three months.
Local chat versus Copilot chat
Here is how the legacy implementation compares to the current state of the extension. Keep in mind that the left side of each line is what we are losing in February 2027.
- Where it runs: Local runs in the VS Code extension host and its code is in the open source VS Code repository, after Microsoft open sourced the Copilot Chat extension under MIT in 2025. Copilot runs in the separate Agent Host process on top of the Copilot SDK. The SDK wrappers are MIT, but the engine that does the actual work is the Copilot CLI, a proprietary binary shipped under the GitHub Copilot CLI License with no public source code.
- Your own models: Local supports Ollama, custom OpenAI compatible endpoints and any provider extension, and it works. Copilot calls it experimental, does not support it in remote sessions at all and in my case it ends with an openssl error.
- Extension tools and chat participants: Local gives the agent the full set of tools provided by your extensions and lets you talk to @participants. Copilot offers a limited set of tools, needs a connected editor window for them and has no chat participants, because that API is deprecated.
- Customizations: Local uses the prompt files, hooks and MCP configuration you already have. Copilot wants prompt files converted to skills, hooks reviewed by hand, MCP servers verified again and secrets entered once more. It is even worse - existing project or workspace skills suddenly become user skills. And who wants to mix all the things between projects, especially since you might have blog writer skills tuned just for certain project.
- Sessions: Credit where it is due, a Copilot session survives closing the window and you can pick it up from another window, from the CLI or from the GitHub app. A Local session dies with the window. This is the one real improvement, and nothing prevented them from adding it to the Local chat. And since I do not use the GitHub App, as I do not have Copilot subscription, this is just not the feature I use.
- Reviewing edits: Local showed you the changes in the editor before they were applied. Copilot writes edits straight to disk from the separate process and the review was rebuilt around a working set. People in the GitHub issue linked below report that they can no longer go through changes file by file the way they used to, and that the whole thing is slower.
- Enterprise control: When your organization sets managed permissions or enables the sandbox, VS Code requires the Copilot chat. This is the real driver of the whole change. The Local chat cannot be controlled from the GitHub side, the Copilot one can. And this was the whole point - I do not want some company in between my local prompt and my BYOK profider.
- Future: Local is deprecated and will be removed in February 2027. Copilot is the only option after that.
So the comparison is a mature, open source chat with working BYOK and full extension support on one side, and an experimental, proprietary runtime with broken BYOK and fewer tools on the other. Microsoft picked the second one for everybody.
Better defaults until February 2027
Until February 2027 you can still get the old behaviour back. The following lines in your settings.json keep the Local chat available and make it the default for new chats:
{
"chat.editor.localAgent.enabled": true,
"chat.defaultToCopilotHarness": false,
"chat.editor.preferCopilotHarness": false
}
If new chats still open in the Copilot tab after that, VS Code remembers the session target you picked last time and this persisted selection wins over the default, so pick Local once from the session target picker. Organization admins get an additional temporary policy for the same thing, which will also be removed in February 2027. Enjoy it while it lasts.
Where does this leave BYOK users?
If you want to keep using your own keys and your own models after February, you will have to look outside of the Copilot stack. The most obvious candidate seems to be OpenCode, an open source coding agent that works with more than 70 providers, with local models through Ollama or LM Studio, and even with an existing Copilot subscription. It has an official VS Code extension, but as far as I can tell it launches the OpenCode terminal interface inside VS Code and shares your selection with it, instead of integrating into the native chat tab. I have not tested the extension yet, so take that with a grain of salt. There is also a third party extension that plugs the OpenCode model gateway into the Copilot model picker, but that again sits on top of the exact stack that is being broken. Cline, Continue and Kilo Code are the usual side panel suspects with their own user interface, their own tool loop and BYOK with local models. None of them is as integrated as the Local chat was, which is the whole point: the only thing that was truly integrated into the editor is the thing that gets deleted.
Microsoft and the open source community, again
The GitHub issue asking to keep the Local harness as an optional extension was opened a week after the announcement, and Microsoft's answer so far is that the Ask agent is back in 1.142 and that we should file separate issues for performance and quality concerns. GitHub user NXY666 wrote a comment there that I can only echo:
If Microsoft doesn't want to keep maintaining Local, then hand it over to the community to maintain. Why completely delete it?
Taking away a mature, usable solution and forcing everyone to migrate to a closed-source replacement is completely unacceptable.
That is exactly it. Nobody asked Microsoft to maintain the Local chat forever. The code is already open source, the people who depend on it are right there in the issue tracker, and keeping it as an optional extension would cost Microsoft nothing. Instead they are taking away a working solution and enforcing their own ecosystem, where every chat goes through a proprietary runtime they control. When Microsoft bought GitHub in 2018 it vowed to keep GitHub open and independent and to be a developer first company. Open sourcing the Visual Studio Code and AI Chat extension looked like that promise still meant something. Deprecating the open part of it a year later, with a three month notice, in favour of a closed binary, shows what the promise is worth. I guess those days are over and Microsoft is again showing us that it is not developer friendly. It is Copilot and profit friendly, and that is not the same thing.
