You Don’t Have to Leave Claude Code to Use DeepSeek

https://hackernoon.imgix.net/images/II97dccrKiSg3Tl3AkxyqvZ77Fq1-i7839cv.png

You do not have to give up Claude Code or Codex CLI to put DeepSeek to work, and you do not have to run a proxy either. Each client has its own documented route to the same API. 🔌

Claude Code -> direct, Anthropic-compatible endpointCodex CLI -> official setup script, Responses APIOpenCode -> /connect, then /modelsAider -> OpenAI-compatible base URLLiteLLM -> one local endpoint, fallback and budgetOllama -> local models, no API at all

Claude Code

For Claude Code:

$env:ANTHROPIC_BASE_URL="https://api.deepseek.com/anthropic"$env:ANTHROPIC_AUTH_TOKEN="sk-YOUR_DEEPSEEK_KEY"$env:ANTHROPIC_MODEL="deepseek-flash[1m]"claude

Everything above the provider stays: the same tools, the same project, the same way of working. Billing moves with the provider, so these requests draw down a DeepSeek balance instead of an Anthropic subscription.

Codex

irm https://cdn.deepseek.com/api-docs/codex-deepseek-setup-en.ps1 | iexcodex

Codex talks to DeepSeek over the Responses API, and the official script writes the provider section for you and backs up the configuration it found. Read it before you run it,...

Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE

Read more