claudecode-deepseek-stack

KO | EN

gitlite — search

#javascript #react #ai #typescript #llm #golang #go #machine-learning #docker #nodejs #windows #awesome #kubernetes #awesome-list

claudecode-deepseek-stack

(★ 77)

Replace Anthropic Claude Code 200/mo billing with DeepSeek V4 for ~7/mo. Two env vars, no third-party tool. Live-tested 95x cheaper.

claudecode-deepseek-stack 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Make Claude Code Free/Cheaper with DeepSeek V4

This guide routes Claude Code's API calls through **DeepSeek V4 instead of Anthropic** — same Claude Code UI, same skills, same workflow.

---

## Setup (5 minutes)

### 1. Get a DeepSeek API key

1. Go to https://platform.deepseek.com
2. Sign up (free, $10 starter credit)
3. Create an API key, copy the value (starts with `sk-`)

### 2. Save the key locally

```bash
mkdir -p ~/.config/mg-deepseek && chmod 700 ~/.config/mg-deepseek
echo 'export DEEPSEEK_API_KEY="sk-your-key-here"' > ~/.config/mg-deepseek/key.env
chmod 600 ~/.config/mg-deepseek/key.env
source ~/.config/mg-deepseek/key.env
```

### 3. Create a Claude Code settings override

Most Claude Code installs already have something configured (Anthropic OAuth login, Vertex AI, AWS Bedrock, or an API key). Inline env-var prefixes get overridden by those configs. The reliable approach is a `--settings` override file.

```bash
cat > ~/.config/mg-deepseek/claude-deepseek-settings.json <<EOF
{
  "env": {
    "CLAUDE_CODE_USE_VERTEX": "",
    "ANTHROPIC_VERTEX_PROJECT_ID": "",
    "CLOUD_ML_REGION": "",
    "ANTHROPIC_DEFAULT_OPUS_MODEL": "",
    "ANTHROPIC_BASE_URL": "https://api.deepseek.com/anthropic",
    "ANTHROPIC_AUTH_TOKEN": "$DEEPSEEK_API_KEY",
    "ANTHROPIC_API_KEY": "$DEEPSEEK_API_KEY"
  }
}
EOF
chmod 600 ~/.config/mg-deepseek/claude-deepseek-settings.json
```

The empty strings on the first 4 keys neutralize Vertex / Bedrock / OAuth-driven defaults. The bottom 3 keys point Claude Code at DeepSeek's Anthropic-compatible endpoint.

### 4. Run Claude Code on DeepSeek

```bash
claude --bare \
  --settings ~/.config/mg-deepseek/claude-deepseek-settings.json \
  --model sonnet \
  "Build me a REST API with auth, JWT, and tests"
```

That's it. Claude Code now talks to DeepSeek V4 Flash (ignore that it says sonnet) for **that one command**. Plain `claude` (without the flags) keeps using your normal backend.

The `--bare` flag is required — it tells Claude Code to read auth strictly from settings, not from OAuth keychain or other auto-detected providers.

### 5. Verify the swap actually fired

```bash
claude --bare --settings ~/.config/mg-deepseek/claude-deepseek-settings.json \
  --debug-file /tmp/check.log --model sonnet "Reply with: SWAP_TEST"
grep "API REQUEST" /tmp/check.log | head -1
```

You should see `/anthropic/v1/messages` in the URL. If you see `/v1/projects/.../publishers/anthropic/...` you're still hitting Vertex; if you see `bedrock-runtime` you're on AWS Bedrock — re-check the JSON file has empty strings for the Vertex / project keys.

---

## Run both backends side-by-side

Two terminals, two backends, simultaneously:

```bash
# Terminal 1 — your normal Claude Code (Vertex / Bedrock / Anthropic API key — unchanged)
claude --model opus "Architect a multi-region failover system"

# Terminal 2 — DeepSeek backend
claude --bare --settings ~/.config/mg-deepseek/claude-deepseek-settings.json \
  --model sonnet "Refactor this codebase to async/await"
```

No conflicts. Different settings sources, different backends, both alive.

---

## Optional: shorten the prefix with an alias

```bash
# Add to your .zshrc or .bashrc
alias claude-cheap='claude --bare --settings ~/.config/mg-deepseek/claude-deepseek-settings.json --model sonnet'
```

Then:

- `claude-cheap "Refactor this"` → DeepSeek V4 Flash (~1¢)
- `claude "Hard problem"` → your default backend

Two commands, two backends, side-by-side in your shell history.

---

## How it works (one paragraph)

Claude Code respects two configuration keys: `ANTHROPIC_BASE_URL` (where to send the API request) and `ANTHROPIC_AUTH_TOKEN` / `ANTHROPIC_API_KEY` (the auth header). DeepSeek exposes an Anthropic-compatible endpoint at `https://api.deepseek.com/anthropic` that speaks the same JSON dialect Claude expects. By providing those keys via `--settings` (which overrides the user-level `~/.claude/settings.json`), you can route a single `claude` invocation to DeepSeek without touching any global config. The `--bare` flag is required because OAuth keychain and auto-detected providers (Vertex AI, AWS Bedrock, Anthropic API key) otherwise win the precedence fight against the env settings.

---

## Notes & troubleshooting

**Use `--model sonnet` or `--model opus`** — Claude Code validates model names against an Anthropic allowlist. The DeepSeek compat endpoint maps the alias server-side (sonnet → DeepSeek V4 Flash by default). You **cannot** pass `--model deepseek-v4-pro` directly; Claude Code rejects it.

**Want DeepSeek V4 Pro specifically?** Pro uses chain-of-thought reasoning and is ~5× slower than Flash for typical coding tasks. For most coding, Flash is the right pick. If you specifically need Pro, call DeepSeek's API directly via curl or Python (bypasses Claude Code's allowlist).

**`Auth conflict` warning when running interactively?** That means Claude Code sees both an env token and a managed login. The `--bare` flag fixes it by ignoring OAuth/keychain — make sure it's in your command.

**Still getting Anthropic responses?** Check the actual API URL with `--debug-file`:
```bash
claude --bare --settings ~/.config/mg-deepseek/claude-deepseek-settings.json \
  --debug-file /tmp/check.log --model sonnet "test"
grep "API REQUEST" /tmp/check.log
```
If the URL contains `projects/.../publishers/anthropic` you're hitting Vertex; if it contains `bedrock-runtime` you're on AWS Bedrock. The override settings file should produce `/anthropic/v1/messages` — if not, the empty-string keys at the top of the JSON aren't doing their job (check JSON syntax, restart shell, re-source the key file).

**Don't `export ANTHROPIC_BASE_URL=...` in `.zshrc`.** Inline env-var prefixes don't actually win the precedence fight when other backends are configured. The `--bare --settings` flag combo is what works reliably.

---

## Resources

- DeepSeek API docs: https://api-docs.deepseek.com
- DeepSeek 75% off pricing page: https://api-docs.deepseek.com/models-pricing
- Claude Code docs: https://docs.anthropic.com/claude/docs/claude-code

claudecode-deepseek-stack

claudecode-deepseek-stack 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

claudecode-deepseek-stack

claudecode-deepseek-stack 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README