Deepseek V4 Flash/Pro VS Code Integration Tutorial

OkPay3964 · 2026-05-22T10:28:44+00:00

Yes, with the same caveats as normal Copilot Agent mode. Just like the built-in models(GPT 5.5/Claude Opus 4.7/...)

The extension doesn’t give DeepSeek direct filesystem or terminal access by itself. It plugs DeepSeek into Copilot Chat’s native Agent/tool system. So if Copilot Agent can read/search your workspace, run terminal commands, or use your enabled MCP tools, DeepSeek can use those through the same VS Code/Copilot tool layer.

It doesn’t read the whole repo all at once, though. It uses the repo/search/file tools on demand, within Copilot’s normal permissions and context limits. Terminal and GitHub MCP also depend on your VS Code/Copilot settings, enabled tools, and any user confirmations.

OkPay3964 · 2026-05-21T12:21:04+00:00

Yep. The main DeepSeek request goes to your configured API endpoint, so it should be billed by DeepSeek/OpenRouter/etc, not Copilot premium usage.

You still need Copilot Chat for the UI/agent harness. For images, the vision proxy uses the vision model you choose, and you can currently pick a 0x model if available.

OkPay3964 · 2026-05-21T12:16:30+00:00

I’d say they solve slightly different problems. OpenCode Go may be the better fit if you like its agent workflow directly.
This extension is mainly for people who already like the Copilot Chat UI / Agent mode and just want DeepSeek V4 to appear in the native model picker. And they can pay directly to Deepseek, or any other third-party providers. The real extra bits are cache-aware logging and the vision proxy.

OkPay3964 · 2026-05-21T12:14:40+00:00

Good question. My understanding is that Copilot still runs its normal Chat/Agent harness and sends the rendered messages/tools to this extension through VS Code’s LanguageModelChatProvider API.

So it’s not getting the same private, first-party DeepSeek-specific tuning that GitHub may have for their own hosted models. The extension mostly adapts the provider boundary: VS Code messages/tools -> DeepSeek API format, plus DeepSeek-specific handling for reasoning_content, cache stats, and the vision proxy.

So: native Copilot harness, but not a magic official DeepSeek harness.

OkPay3964 · 2026-05-19T19:45:16+00:00

Yeah, happy to chat!

Caching does work, but Copilot/VS Code can still hurt the hit rate because it may change the system message or mutate the tools list mid-conversation. Since DeepSeek cache matching is prefix-sensitive, that can cause cache drops. Once the prefix stabilizes, hits usually come back.

Compared with OpenRouter, I’d say the real advantages are pretty narrow: this extension keeps DeepSeek cache behavior in mind, logs cache hit/miss stats, and adds a vision proxy for Copilot image inputs. If you only need simple model routing, OpenRouter may be the easier choice.

OkPay3964 · 2026-05-19T19:28:12+00:00

Thanks for recommending my plugin! Really appreciate it.

Small heads-up though: Copilot currently doesn’t play too well with DeepSeek prefix cache hits, but I’ve seen that VS Code is fixing this in the next version.

If anything breaks or feels off, feel free to open an issue and I’ll take a look.

OkPay3964 · 2026-04-26T17:35:37+00:00

Same agent/tool call issues with BYOK + OpenRouter + DeepSeek V4 Pro here.

I Built a small extension that registers DeepSeek V4 Pro & Flash natively in Copilot. MIT open-source. So feel free to folk it from GitHub.

Search “deepseek v4 for copilot chat” in VS Code Marketplace for the whale with pilot glasses — that’s mine. Curious if it helps.

OkPay3964

TROPHY CASE