There’s a recurring confusion worth clearing up first: Claude Code and Claude Desktop are different things. Claude Code is the terminal CLI and accepts any compatible model with two environment variables. Claude Desktop is the GUI app, built around Anthropic’s own service, and it doesn’t hand you a model picker for third parties. To run DeepSeek behind the desktop app, you use a community helper.
This explains the distinction, walks through the desktop route with a switch tool, and — honestly — points you to the simpler CLI path if that’s really what you want. For that, see run DeepSeek with Claude Code.
Desktop vs Code: pick the right target
Claude Desktop vs Claude Code
| Claude Code (CLI) | Terminal; native ANTHROPIC_BASE_URL support; easiest for DeepSeek |
|---|---|
| Claude Desktop (GUI) | App; no built-in provider picker; needs a helper tool |
The desktop route with a switch tool
Community tools exist to point the desktop app at alternative providers. One example is cc-desktop-switch, a lightweight helper for configuring DeepSeek, Kimi, Zhipu GLM, and similar providers for desktop use by managing the endpoint and key settings.
The general flow:
- Get a DeepSeek API key from the DeepSeek platform.
- Install the switch tool from its GitHub repository, following its README.
- Use it to set the provider to DeepSeek, paste your key, and choose the model (
deepseek-chatordeepseek-reasoner). - Restart the desktop app so it picks up the new settings.
Pick the model
The same DeepSeek models apply:
deepseek-chat— general use, fastest and cheapest.deepseek-reasoner— thinking mode for harder problems.
The switch tool lets you set which one the desktop app targets.
Pricing
DeepSeek is pay-per-token with no coding plan; the helper tools are free. Your cost is DeepSeek’s low token rate, with cache-hit discounts and off-peak windows. Confirm current rates on the official pricing page — see DeepSeek V4 pricing explained.
The honest recommendation
If the goal is cheap coding with DeepSeek, the desktop app is the harder road. The CLI (Claude Code) is a clean two-variable setup, and editor extensions like Cline give a GUI workflow that’s purpose-built for third-party models. Reach for the desktop switch only if the desktop chat UI is specifically what you want.
If you go the desktop route
- Confirm you want Desktop (GUI), not Code (CLI)
- Get a DeepSeek API key
- Install a reputable switch tool from GitHub; read its README
- Set provider to DeepSeek, key, and model
- Restart the app; verify it routes to DeepSeek
Wrapping up
Claude Desktop doesn’t natively support third-party models, so running DeepSeek behind it means using a community switch tool to manage the endpoint and key, then restarting the app. It works, but it’s the harder path and depends on a community project. For cheap DeepSeek coding, the CLI (Claude Code) or an editor extension (Cline) is simpler and better supported.
For the cost side, see DeepSeek V4 pricing explained.
