musistudio/claude-code-router is a TypeScript project with 38.1k stars. One local control plane for every AI agent: route across models, fuse new capabilities, orchestrate tools, and stay fully in control.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Connect Claude Code, Claude Design, Codex, Grok CLI, Kimi CLI, Kilo Code, OpenCode, Pi, ZCode, WorkBuddy, and compatible API clients to the providers you choose—then route, fail over, extend, and observe every request from one app.
Why use Claude Code Router?
Claude Code Router (CCR) is a local model gateway and control plane for coding agents. It gives Claude Code, Claude Design, Codex, Grok CLI, Kimi CLI, Kilo Code, OpenCode, Pi, ZCode, WorkBuddy, and compatible API clients one stable local endpoint, while you manage the providers, models, accounts, routing rules, and tools behind it from one place.
Use CCR to:
Manage all agents and providers together instead of maintaining a separate model configuration for every client.
Switch providers or models without changing your workflow or repeatedly editing agent configuration files.
Keep requests running with retries, credential pools, key rotation, and ordered fallback models.
Add capabilities to existing models with Fusion vision, web search, MCP tools, and ToolHub.
See what actually happened through request logs, resolved routes, latency, token usage, cost estimates, and account status.
Download Claude Code Router for macOS, Windows, or Linux, then launch the app.
Windows
Linux
macOS (Apple Silicon)
macOS (Intel)
Open Providers → Add Provider. Choose a built-in preset or a custom endpoint, enter the API key, select the protocol and models, then save.
Open Server and click Start. The local model gateway listens on http://127.0.0.1:3456 by default.
Open Agent Config, choose Claude Code, Claude Design, Codex, Grok CLI, Kimi CLI, Kilo Code, OpenCode, Pi, ZCode, or WorkBuddy, select a model, and apply the profile.
Start using your agent. Open Logs to confirm the resolved provider, model, status, tokens, latency, and errors.
Your agent is now connected to CCR. To add conditions, retries, request rewrites, or fallback models, open Routing.
CLI
The npm CLI requires Node.js 22 or newer. It starts the same gateway and a browser-based management UI without Electron:
Open http://127.0.0.1:3458, then follow the same Providers → Server → Agent Profiles flow above. The model gateway remains at http://127.0.0.1:3456. See the CLI reference for service modes, authentication, and profile commands.
Docker
npm run docker:compose:up
Docker exposes the management UI and gateway routes through http://127.0.0.1:3458 by default. The npm script prepares the local plugin-capable ai-gateway runtime before building the image when ../../next-ai/gateway exists. Read the Docker deployment guide before exposing CCR remotely.
Build desktop apps
Install Node.js 22+, then run npm ci.
Target
Command
Output
macOS local DMG/ZIP
npm run build:app:mac
release-local/
Windows local NSIS installer
npm run build:app:win
release-local/
Windows app packaging must run on Windows x64 because better-sqlite3 ships a native Electron module. The release workflow builds macOS on macOS runners and Windows on windows-latest when a v* tag is pushed.
How it works
Claude Code · Claude Design · Codex · Grok CLI · Kimi CLI · Kilo Code · OpenCode · Pi · ZCode · WorkBuddy · Compatible API clients
│
▼
Claude Code Router :3456
Profiles · Routing · Credentials · Tools · Logs
│
▼
Selected provider, model, and account
Core capabilities
Area
Highlights
Agents
Profiles for Claude Code, Claude Design, Codex, Grok CLI, Kimi CLI, Kilo Code, OpenCode, Pi, ZCode, and WorkBuddy; model overrides; scopes; environment settings; CLI and app launch entries; multi-instance workflows
Providers
Presets and custom endpoints; protocol probing; model discovery; connectivity checks; local login import where supported; single keys and credential pools
Models & routing
Searchable catalog; model descriptions for task selection; conditions on headers and bodies; prefixes; rewrites; retries; ordered fallbacks
Tools & extensions
Fusion models; ToolHub; built-in browser automation; Chrome login-state import; wrapper and core gateway plugins; local routes and virtual models
Access & quotas
Separate CCR client keys with expiration and local request, token, and image limits
Observability
Request and response details; resolved provider, model, and credential; status; latency; tokens; estimated cost; tool calls; agent traces
AgentClaw
Agent relay through Weixin iLink, WeCom, Slack, Discord, Telegram, LINE, Feishu, and DingTalk
Go deeper when you are ready
The complete documentation lives at ccrdesk.top.
Install and launch CCR
Configure providers
Explore routing and configuration
Use the CLI
Deploy with Docker
Troubleshoot common issues
Support & Sponsoring
If you find this project helpful, please consider sponsoring its development. Your support is greatly appreciated.
One-time support via Ko-fi
International sponsorship
Alipay
WeChat Pay
Our Sponsors
A huge thank you to all our sponsors for their generous support.
Z智谱
AIHubmix
BurnCloud
302.AI
RunAPI
TeamoRouter
code0.ai
claudeapi
Qiniu Cloud AI
Fenno.ai
Unity2.Ai
无限星河
Community Sponsors
@Simon Leischnig
@duanshuaimin
@vrgitadmin
@*o
@ceilwoo
@*说
@*更
@K*g
@R*R
@bobleer
@*苗
@*划
@Clarence-pan
@carter003
@S*r
@*晖
@*敏
@Z*z
@*然
@cluic
@*苗
@PromptExpert
@*应
@yusnake
@*飞
@董*
@*汀
@*涯
@*:-)
@**磊
@*琢
@*成
@Z*o
@*琨
@congzhangzh
@*_
@Z*m
@*鑫
@c*y
@*昕
@witsice
@b*g
@*亿
@*辉
@JACK
@*光
@W*l
@kesku
@biguncle
@二吉吉
@a*g
@*林
@*咸
@*明
@S*y
@f*o
@*智
@F*t
@r*c
@qierkang
@*军
@snrise-z
@*王
@greatheart1000
@*王
@zcutlip
@Peng-YM
@*更
@*.
@F*t
@*政
@*铭
@*叶
@七*o
@*青
@**晨
@*远
@*霄
@**吉
@**飞
@**驰
@x*g
@**东
@*落
@哆*k
@*涛
@苗大
@*呢
@d*u
@crizcraig
s*s
*火
*勤
**锟
*涛
**明
*知
*语
*瓜
**新
If your name is masked, please contact me via my homepage email to update it with your GitHub username.
TopGit's last sync did not record any GitHub topics for musistudio/claude-code-router. GitHub topics appear in the right sidebar of a repository page; that's the authoritative place to check.
How active is development on musistudio/claude-code-router?
The most recent commit recorded on musistudio/claude-code-router was 1 month ago, based on the GitHub push timestamp. The repository has 3.2k forks — one of the better signals of community interest.
How many stars does musistudio/claude-code-router have?
musistudio/claude-code-router has 38.1k GitHub stars — refresh the page for the live number, or check github.com/musistudio/claude-code-router. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is musistudio/claude-code-router written in?
musistudio/claude-code-router is written primarily in TypeScript. GitHub's language field is based on the largest share of bytes in the default branch.
What license does musistudio/claude-code-router use?
musistudio/claude-code-router is released under the MIT license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
Where can I see musistudio/claude-code-router in action?
The project maintains a homepage at https://ccrdesk.top/. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about musistudio/claude-code-router?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/musistudio/claude-code-router is the definitive source.
Read full README in the tab above.
Curious whether claude-code-router is right for you?
Let ChatGPT, Claude, or Perplexity look into it — click below and see what AI actually says about claude-code-router.