DeepSeek Claude Code Needs V4 Model Pins Before July 24

Migrated with permission from DeepSeek V4 Pro, a related editorial property operated by our team.

DeepSeek's official docs now tie Claude-style integrations more clearly to exact V4 model strings, while the main API quick-start warns that deepseek-chat and deepseek-reasoner will be deprecated on July 24, 2026.

DeepSeek's official Claude Code page still gives the same Anthropic-compatible baseline that this site already recommends, but the broader official API docs now add an important migration warning that older community tutorials can easily miss: deepseek-chat and deepseek-reasoner are scheduled to be deprecated on July 24, 2026.

What changed upstream

The official Claude Code recipe still expects exact V4 strings: ANTHROPIC_MODEL=deepseek-v4-pro[1m], the matching ANTHROPIC_DEFAULT_* pins, CLAUDE_CODE_SUBAGENT_MODEL=deepseek-v4-flash, and CLAUDE_CODE_EFFORT_LEVEL=max.

The official API quick-start now flags legacy aliases with a real date: deepseek-chat and deepseek-reasoner are marked for 2026-07-24 deprecation.

The compatibility mapping is now explicit: the same quick-start says those old names only exist for compatibility and currently map to the non-thinking and thinking modes of deepseek-v4-flash, respectively.

The Anthropic-format warning still matters: DeepSeek's Anthropic API docs say unsupported model names can automatically map to deepseek-v4-flash. That means outdated aliases or altered provider-side names can silently leave a Claude Code or Desktop workflow on Flash when the user expected Pro.

Practical setup guidance

This is not just a naming nit. It changes what a trustworthy DeepSeek-via-Claude setup guide should tell developers to do right now:

1. Copy the official V4 model strings exactly instead of reusing older deepseek-chat or deepseek-reasoner snippets. 2. Treat July 24, 2026 as the migration deadline for any Claude Code, Claude Desktop, Gateway, or settings.json workflow still using those aliases. 3. Verify provider-side model usage when testing Desktop mapping or "Cloud Code" wording variants, because unsupported names can still fall back to Flash.