# Claude Code Router — Multi-Provider CLI Gateway > Claude Code Router routes Claude Code requests across providers and transformers. Configure ~/.claude-code-router for proxies, logs, and model rules. ## Install Copy the content below into your project: ## Quick Use 1. Install the verified package or repo entrypoint: ```bash npm install -g @anthropic-ai/claude-code npm install -g @musistudio/claude-code-router ``` 2. Run the first local check: ```bash mkdir -p ~/.claude-code-router $EDITOR ~/.claude-code-router/config.json ``` 3. Add a repeatable verification command: ```bash ccr --help ``` --- ## Intro Claude Code Router is a verified GitHub-backed tool for modern AI and developer workflows, sourced from `musistudio/claude-code-router` with 33,803 stars and a MIT license snapshot. Best for: Claude Code power users who need provider routing, proxy rules, request logging, or custom model transforms without changing project code. Works with: Claude Code, npm global installs, provider API keys, proxy URLs, per-model routing rules. Setup time: 10 minutes. Use it when you need a concrete, repeatable path rather than another one-off shell snippet. --- ## Operating Pattern ### Fit check | Question | Practical answer | |---|---| | What do you install? | `@musistudio/claude-code-router` from `musistudio/claude-code-router` | | What is the first command? | `mkdir -p ~/.claude-code-router` | | What proves it works? | `ccr --help` | | How long should a pilot take? | 10 minutes for a small repo or sandbox | ### Adoption loop 1. Run the tool on a disposable branch or sandbox project. 2. Capture before/after output so reviewers can see the exact effect. 3. Add the smallest CI or local check that prevents regressions. 4. Document owner, upgrade command, and rollback command in the repo. ### Recommended use Treat the router as local coding infrastructure: keep config in a private dotfiles repo, test one provider at a time, and log only what your team is allowed to retain. ### Guardrails Do not commit `~/.claude-code-router/config.json`; it can contain model keys, proxy endpoints, and routing decisions that belong outside the app repository. ### Rollout checklist - Pin the package or release version before using it in CI. - Keep credentials in environment variables or the platform secret store. - Add one owner who is responsible for upgrades and breaking-change triage. - Re-check the GitHub repo before writing docs that mention APIs or install paths. --- ### FAQ **Q: Is this production-ready?** A: The repo exists at `https://github.com/musistudio/claude-code-router` and has 33,803 GitHub stars. Treat the first rollout as a controlled pilot until your team has tested install, rollback, and CI behavior. **Q: Why use it instead of a generic script?** A: The value is repeatability: a named package, a documented command, a source repo, and a small verification path that can be reviewed by teammates. **Q: What should I measure first?** A: Measure setup time against the 10 minutes target, count how many files or tasks it changes, and record whether the CI command catches the same issue locally. --- ## Source & Thanks > Built from [musistudio/claude-code-router](https://github.com/musistudio/claude-code-router). License: MIT. > > GitHub stars verified from `api.github.com/repos/musistudio/claude-code-router`: 33,803. --- ## 快速使用 1. 安装已验证的包或仓库入口: ```bash npm install -g @anthropic-ai/claude-code npm install -g @musistudio/claude-code-router ``` 2. 跑第一次本地检查: ```bash mkdir -p ~/.claude-code-router $EDITOR ~/.claude-code-router/config.json ``` 3. 加一个可重复验证命令: ```bash ccr --help ``` --- ## 简介 Claude Code Router 是一个已通过 GitHub 仓库验证的现代 AI / 开发者工具,来源 `musistudio/claude-code-router`,当前星标快照 33,803,许可证 MIT。适合:需要供应商路由、代理规则、请求日志或自定义模型转换,但不想改项目代码的 Claude Code 重度用户。兼容:Claude Code、npm 全局安装、供应商 API key、代理 URL、按模型路由规则。装机时间:10 minutes。当你需要的是可重复落地路径,而不是一次性 shell 片段时,用它。 --- ## 操作模式 ### 适配检查 | 问题 | 实用答案 | |---|---| | 安装什么? | 来自 `musistudio/claude-code-router` 的 `@musistudio/claude-code-router` | | 第一条命令? | `mkdir -p ~/.claude-code-router` | | 如何证明可用? | `ccr --help` | | 小范围试点多久? | 小仓库或 sandbox 约 10 minutes | ### 接入循环 1. 先在一次性分支或 sandbox 项目里跑。 2. 记录 before / after 输出,让 reviewer 看见实际影响。 3. 加最小的 CI 或本地检查,防止同类问题回归。 4. 在仓库文档里写清 owner、升级命令和回滚命令。 ### 推荐用法 把 router 当成本地编码基础设施:配置放进私有 dotfiles,一次只测试一个供应商,只记录团队允许保留的日志。 ### 风险边界 不要提交 `~/.claude-code-router/config.json`;里面可能有模型 key、代理端点和路由策略,应该留在应用仓库之外。 ### 推广检查表 - 进入 CI 前固定包版本或 release 版本。 - 凭据放进环境变量或平台 secret store。 - 指定一个 owner 负责升级和 breaking change 分流。 - 文档里写 API 或安装路径前,重新核验 GitHub 仓库。 --- ### FAQ **Q: 能直接上生产吗?** A: 仓库已验证存在:`https://github.com/musistudio/claude-code-router`,GitHub 星标 33,803。第一次上线仍建议控制试点,先验证安装、回滚和 CI 行为。 **Q: 为什么不用普通脚本?** A: 价值在可重复:有命名包、文档化命令、源仓库和可被团队 review 的最小验证路径。 **Q: 第一步应该量什么?** A: 先量装机时间是否接近 10 minutes,它改了多少文件或任务,以及 CI 命令是否能在本地抓到同类问题。 --- ## 来源与感谢 > 来源:[musistudio/claude-code-router](https://github.com/musistudio/claude-code-router)。许可证:MIT。 > > GitHub stars 已通过 `api.github.com/repos/musistudio/claude-code-router` 验证:33,803。 --- Source: https://tokrepo.com/en/workflows/claude-code-router-multi-provider-cli-gateway Author: musistudio