Claude Code Router

This is a repository for testing routing Claude Code requests to different models.

Usage

1. Install Claude Code

npm install -g @anthropic-ai/claude-code

2. Install Claude Code Router

npm install -g @musistudio/claude-code-router

3. Start Claude Code by claude-code-router

ccr code

Plugin

The plugin allows users to rewrite Claude Code prompt and custom router. The plugin path is in $HOME/.claude-code-router/plugins. Currently, there are two demos available:

1. custom router
2. rewrite prompt

You need to move them to the $HOME/.claude-code-router/plugins directory and configure 'usePlugin' in $HOME/.claude-code-router/config.json，like this:

{
    "usePlugin": "gemini",
    "LOG": true,
    "OPENAI_API_KEY": "",
    "OPENAI_BASE_URL": "",
    "OPENAI_MODEL": ""
}

Features

• Plugins
• Support change models
• Suport scheduled tasks

Some tips:

If you’re using the DeepSeek API provided by the official website, you might encounter an “exceeding context” error after several rounds of conversation (since the official API only supports a 64K context window). In this case, you’ll need to discard the previous context and start fresh. Alternatively, you can use ByteDance’s DeepSeek API, which offers a 128K context window and supports KV cache.

Note: claude code consumes a huge amount of tokens, but thanks to DeepSeek’s low cost, you can use claude code at a fraction of Claude’s price, and you don’t need to subscribe to the Claude Max plan.

Some interesting points: In my testing, providing absolute context information can help bridge the gap between these models. For example, when I used Claude 4 in VS Code Copilot to handle a Flutter issue, after three rounds of conversation it kept messing up the files, and I had to roll back in the end. But when I switched to claude code using DeepSeek, after three or four rounds of conversation, I finally completed my task—and the cost was less than 1 RMB!