Developer2026-07-02

DeepSeek has a clean Claude Code route, while Codex still needs custom-provider caution for V4 thinking mode

Checked on July 2, 2026: DeepSeek's official Claude Code path is clear: Anthropic endpoint, V4 Pro main model, Flash subagent lane, Web Search, and Claude-name mapping. Codex is different. Current openai/codex issue reports show DeepSeek V4 thinking-mode, Desktop model picker, profile routing, and auto-review friction, so it should be written as a custom-provider watchlist rather than a confirmed DeepSeek Codex integration.

What changed after the June Claude Code item

Claude Code is no longer the messy part of the story. DeepSeek's own docs give teams a direct Anthropic-compatible route: point Claude Code at https://api.deepseek.com/anthropic, use deepseek-v4-pro[1m] for the main lane, keep deepseek-v4-flash for subagents, and set the effort level to max.

That is still worth a fresh update because the same DeepSeek page now carries three practical details that older community snippets often miss: Web Search can run through DeepSeek, Claude-style model names can map to V4 Pro or V4 Flash, and search-triggered summarization costs extra model tokens. This is a setup contract, not just a screenshot walkthrough.

Codex is a different story

Do not call Codex an official DeepSeek integration yet. No matching DeepSeek agent-integration page for OpenAI Codex showed up in the official docs checked for this update. The current signal is narrower and more operational: developers are trying DeepSeek through Codex custom providers, and the openai/codex issue tracker shows where that path still catches.

  • DeepSeek thinking mode can fail in multi-turn Codex sessions if reasoning_content is not passed back after tool-use turns.
  • Codex Desktop has separate reports around custom-provider model catalogs and picker visibility, especially when users expect GUI switching instead of manual config.toml edits.
  • A June report says Codex CLI 0.14.0 ignored --profile and custom model_providers in one setup, falling back to OpenAI instead of the configured DeepSeek-shaped provider.
  • Another report says Codex auto-review can send codex-auto-review to a custom DeepSeek provider, which DeepSeek rejects because it only recognizes its own V4 model names.

Those are useful developer signals, but they are not the same as DeepSeek saying 'Codex is supported' in its docs. The honest headline is: Claude Code has the official path; Codex is possible only through custom-provider work, and the rough edges are still visible.

How to use this on the site

Do not write another generic Claude Code setup page just to chase freshness. The existing Claude Code and Anthropic-routing pages already cover the official route. The useful addition is the boundary: when readers ask about Codex, point them to the OpenAI-format route, DeepSeek V4 model names, and the known custom-provider risks instead of promising a polished first-party flow.

This also keeps the commercial line clean. None of these sources creates a new stocked Coding Plan, a new provider card, or a plan migration. It is content and troubleshooting coverage only.

Sources checked

View original source