Official2026-06-25

DeepSeek's official Anthropic API guide now makes Claude-name mapping explicit, warns that unsupported model names silently fall back to `deepseek-v4-flash`, and frames the rule as a real Claude Desktop developer-mode boundary

Checked on June 25, 2026: DeepSeek's official Anthropic API page says `claude-opus*` maps to V4 Pro, `claude-haiku*` and `claude-sonnet*` map to V4 Flash, unsupported model names automatically fall back to Flash, and the mapping can help bypass Claude Desktop developer-mode model-name restrictions.

Accepted official-source monitoring note

Today's accepted item stays DeepSeek-first and uses a current official DeepSeek documentation page because the official @deepseek_ai X surface still was not safely readable in this run. DeepSeek's English homepage still anchors the official X account through the V4 Preview banner, but the direct timeline did not expose a reliably crawlable current post here, so the publish-safe choice is a first-party docs-backed developer update.

What we verified on June 25, 2026

  • DeepSeek's official Anthropic API guide publishes an explicit Claude-name mapping rule: claude-opus* routes to deepseek-v4-pro, while claude-haiku* and claude-sonnet* route to deepseek-v4-flash.
  • The same official page warns that unsupported model names are not rejected hard by default. DeepSeek says the Anthropic API backend will automatically map an unsupported model name to deepseek-v4-flash.
  • DeepSeek also frames this mapping as useful inside the new Claude Desktop app's developer mode: the docs say that by changing only the base URL and API key, users can bypass the app's model-name restrictions and still connect to DeepSeek models.
  • The official endpoint contract remains simple: https://api.deepseek.com/anthropic with Anthropic-style clients, rather than inventing a separate DeepSeek-only SDK surface for this workflow.

Why this is publishable

This is a current official DeepSeek support page, not a rumor, repost, or inventory claim.

  1. It upgrades a common community workaround into a first-party routing rule with exact mapping behavior.
  2. It documents a real operational risk: a model string can look accepted in the client while the backend silently serves Flash instead of Pro.
  3. It directly affects Claude Code, Claude Desktop developer mode, and any Anthropic-style SDK setup that sends Claude-shaped model names to DeepSeek.
  4. It is not a duplicate of the June 24 Copilot CLI item because today's story is about provider-side model mapping and Flash fallback behavior, not Copilot CLI's reasoning_content replay failure.

Why this matters for DeepSeek-first SEO pages

  • Support pages can now target official DeepSeek Anthropic model mapping instead of vague 'Claude-compatible' claims.
  • DeepSeek-first setup guides can explain why unsupported model strings are dangerous even when a request appears to succeed.
  • Claude Desktop and Claude Code tutorials can now separate official facts from analysis around routing, Flash fallback, and Pro verification.

Rejected candidates today

  • Official X timeline as the primary source: rejected for this run because the homepage still anchored DeepSeek's X presence, but the direct X surface remained unreadable here.
  • The official OpenCode and OpenClaw pages: official, but already used earlier in the week as direct documentation-backed news items, so they were weaker repeat candidates.
  • The official Thinking Mode guide: official and useful, but weaker for the single news slot because the model-mapping and silent Flash fallback rule is narrower, more operationally surprising, and more publication-worthy today.
  • The homepage V4 Preview X anchor: official, but older and already covered in existing launch and migration content.
  • Status-page uptime alone: official, but weaker than a docs page that changes how developers verify the actual model route behind Anthropic-format clients.
  • Official GitHub and Hugging Face surfaces: checked as backup official sources, but no newer first-party developer update beat the Anthropic API guide for today's publish-safe slot.

Editorial takeaway

The safest official DeepSeek story today is an Anthropic API routing contract check: DeepSeek's own docs now publish the Claude-name mapping rule, the automatic Flash fallback behavior for unsupported model names, and the developer-mode positioning for Claude Desktop. That is a stronger current developer signal than recycling an older X anchor we still could not fully verify live.

Sources checked

View original source