DeepSeek's official GitHub Copilot guide now documents a DeepSeek V4 chat extension with Pro, Flash, MCP, and optional vision proxy support

Checked on June 14, 2026: DeepSeek's official GitHub Copilot integration page now documents a VS Code extension that adds DeepSeek V4 Pro and Flash to Copilot Chat, keeps agent mode, tool calling, skills, and MCP, and adds an optional vision proxy path.

英文原文

这篇动态暂时没有完整中文稿。为了避免中文 SEO 页面收录英文正文，详情页会标记为 noindex。

Accepted official-source monitoring note

Today's accepted item stays DeepSeek-first and uses current official DeepSeek documentation because the public X surface is still login-friction-heavy and did not expose a newer safely verifiable post than the homepage anchor that was already covered earlier this week.

What we verified on June 14, 2026

DeepSeek now has an official GitHub Copilot integration page in its API docs for a VS Code extension called DeepSeek V4 for Copilot Chat.
That official page says the extension adds DeepSeek V4 Pro and DeepSeek V4 Flash directly into the GitHub Copilot Chat model picker.
The same official page says users keep Copilot's agent mode, tool calling, skills, and MCP while routing model work to DeepSeek.
DeepSeek also documents optional thinking-effort controls with None, High, and Max choices inside the model picker.
The same page documents an optional vision-proxy path: when a screenshot is dropped into chat, another installed Copilot model can describe the image before forwarding text to DeepSeek, because DeepSeek V4 itself is text-only.
DeepSeek's English homepage still points its public social anchor to @deepseek_ai, which remains the safest official X-account confirmation even though the X page itself is not safely crawlable here.

Why this is publishable

This is not framed as a new stocked product or a broad market rumor. It is a current official developer-integration signal that matters for real DeepSeek adoption:

It shows DeepSeek is documenting a first-party path into a major coding surface beyond Claude Code.
It gives a concrete official workflow for teams that already live inside VS Code and Copilot Chat.
It adds a new official docs topic that is not a duplicate of the June 10 Claude Code Web Search page or the June 11 rate-limit docs check.

Why this matters for DeepSeek-first SEO pages

GitHub Copilot comparison and migration pages can now reference an official DeepSeek integration surface, not just generic OpenAI-compatible API swaps.
Setup guides should explain that DeepSeek V4 remains text-only, even when the extension can proxy image descriptions through another installed Copilot model.
Cost-control pages should keep Pro-versus-Flash routing visible, because the extension exposes both choices inside Copilot Chat.

Rejected candidates today

The same April 24 homepage X anchor: still official, but already published and therefore a duplicate-content risk.
The June 10 Claude Code Web Search page: still official, but already covered in the current news set.
Status page uptime alone: official, but weaker and less actionable than the current GitHub Copilot integration page.
Community posts about Copilot alternatives or unofficial extensions: useful discovery leads only, but weaker than the official DeepSeek docs page that states the integration contract directly.

Editorial takeaway

The safest official DeepSeek story today is a GitHub Copilot integration documentation check: DeepSeek's own docs now describe a VS Code extension that places V4 Pro and V4 Flash inside Copilot Chat, keeps Copilot's agent features and MCP, and exposes a vision-proxy fallback without pretending DeepSeek V4 is natively multimodal.