
37.9k stars · MIT, named in the About sidebar · v3.1.3, confirmed from the npm registry entry for @musistudio/claude-code-router, published in October 2026 · Track this in Scout
One local address that many coding assistants can talk to, pointed at whichever model the operator chooses.
Radar check
What we found when we opened it. Every bar is one fact, with its date.
Last code pushed 10 Oct 2026, 17 days before this check.
Latest release v3.1.3 on 9 Oct 2026.
Public since February 2025, a little over 1 year.
37,873 stars and 3,178 forks.
252 commits and 161 new issues in the last 90 days.
72 contributors. 54 pull requests merged in 90 days.
No security policy file says how to report a problem. 1 published security advisory.
How the bars are scored
- Alive. Days since the last code push: a week or less 100, a month 90, three months 70, six months 50, a year 30, eighteen months 15, older 0.
- Releases. Age of the latest GitHub release, on a similar scale; no bar when the project publishes no releases.
- Maturity. Age of the project: eight years 100, five 90, three 70, two 55, one 40, six months 25, younger 10.
- Adoption. Stars on a log scale: 100,000 stars is 100, 10,000 is 80, 1,000 is 60, 100 is 40.
- Activity. Commits in the last 90 days: 300 or more 100, 100 85, 30 65, 10 45, any 25.
- Community. People who have contributed: 100 or more 100, 30 80, 10 60, 5 40, 2 25, one 10.
- Security. A published security policy 80, none 40; published advisories are listed, not scored.
Checked by Repo Radar on 27 Oct 2026 from the repository on GitHub. Covered in Edition 63.
▶Repo detailsthe review · specs · pros & cons · install
What it does
It runs a small service on the machine, by default on port 3456, and a management page on port 3458. Coding assistants are configured to send their requests to that address instead of to a supplier. It speaks several request formats on both sides, including the OpenAI chat and responses formats, the Anthropic messages format and Gemini, and it can forward to suppliers such as OpenRouter, DeepSeek, Mistral and Moonshot. Routing rules can read the headers and body of a request, so short completions and long reasoning can go to different models. It holds pools of credentials, rotates keys, retries, and falls back down an ordered list of models when one is unavailable. It records every request with the model chosen, the delay, the tokens used and an estimated cost. It issues its own keys with expiry dates and limits, so a shared instance can be handed out safely. It is not a model and it is not an assistant: nothing here writes code, and without at least one supplier key it does nothing at all.
Why it matters
Who it suits. Anyone using more than one coding assistant, or more than one model supplier, and tired of keeping keys in several places. It also suits anyone who wants to know what the month's model use actually cost, broken down by request. Skip it if there is one assistant and one supplier and the bill is already clear: this adds a moving part for no gain.
Verdict. The cost accounting is the part that earns its keep. Model spending is hard to see and easy to let run, and a log that names the model, the tokens and the estimated cost for every request changes behaviour. The scope is the worry. The project has grown far past routing into browser automation, plugins and relays through eight different chat platforms, which is a lot of ground for one project with 942 open issues. Node.js 22 or newer is required. If the need is a plain gateway in front of many models with nothing else attached, BerriAI/litellm and Portkey-AI/gateway are narrower and calmer choices.
- Per-request logs with model, delay, tokens and estimated cost.
- Ordered fallback models and key rotation, so one supplier failing is not a stoppage.
- Its own client keys with expiry and limits, which makes a shared instance practical.
- The project does a great deal besides routing, and 942 open issues suggest the breadth has a price.
- Needs Node.js 22 or newer, which is more recent than many systems ship.
- Packaging the Windows desktop build must happen on Windows, because of a compiled component.
BerriAI/litellmA gateway that calls a hundred or more model services in one format; a library and a proxy rather than a desktop control room.
Track this in Scout- Portkey-AI/gateway
Routes to a large catalogue of models with content checks attached; strong on guardrails, no agent features.
Track this in Scout
npm install -g @musistudio/claude-code-router ccr ui



