A lot of older third-party Claude model routes have become unreliable. I tested a narrower path on Windows: Claude Code through cc-switch to DeepSeek.

Important boundary first: cc-switch is not a Claude jailbreak, and it is not a universal adapter for every coding agent. It mainly helps with the Claude Code provider route. Codex cannot use this path directly.

What cc-switch actually solves

It reduces manual config drift.

Instead of hand-editing model name, base URL, and API key every time, you keep them as named providers and switch between them.

The package I used:

npm install -g @adithya-13/cc-switch

Windows traps

Two details mattered in my test.

First, PowerShell may block the npm-generated .ps1 shim. When that happens, try:

cmd /c cc-switch

Second, do not save the provider JSON config with a BOM. I hit a JSON parsing failure that disappeared after saving the config as UTF-8 without BOM.

Verification

I would not call the route ready until:

Active: DeepSeek

is visible, and the doctor check passes.

Only then did I restart Claude Code and test a small task.

Takeaway

This path is useful if you already use Claude Code and want a cleaner DeepSeek provider setup on Windows.

It is not a general solution for every agent. The practical value is narrower: make the provider state visible, avoid hand-edited config drift, and keep Windows shell/encoding issues from masquerading as model failures.