Privacy and advertising choices
Git-Stars uses essential storage for site operation. Optional analytics and ad-measurement scripts stay disabled unless you accept them; partners such as Google may then use cookies or similar identifiers where required. Privacy Policy
One local control plane for every AI agent: route across models, fuse new capabilities, orchestrate tools, and stay fully in control.
This repository page has enough original analysis, source evidence, and comparison context to be treated as an indexable Git-Stars review.
100
review score
Problem solved
CCR solves the fragmentation of managing separate model configurations for each coding agent (e.g., Claude Code, Codex, Grok CLI) by centralizing provider management, routing, and observability. It eliminates the need to repeatedly edit agent config files when switching models or providers, and adds resilience through retries, credential pools, and fallback models.
Deployment reality
The available setup signal starts with: Download the desktop app from the GitHub releases page.. Treat this as a starting point, then ask Codex or Claude to inspect the README, environment variables, runtime version, and deployment target before production use.
Commercial use
The recorded license is MIT. This is a useful commercial-use signal, but teams should still verify license text, dependencies, model/API terms, and trademark constraints.
Capability ceiling
Developers can build multi-agent workflows that route requests across different models and providers, fuse capabilities like vision and web search into existing agents, orchestrate MCP tools and ToolHub, and monitor all activity through request logs, latency, token usage, and cost estimates. Real-world use cases include failover between Anthropic and OpenAI models, pooling API keys for rate limit avoidance, and extending Claude Code with custom tools without modifying its configuration.
Git-Stars is independent and not affiliated with GitHub or this project. Analysis may be AI-assisted and based on public repository metadata plus short README-derived summaries. We do not mirror full README files, docs, issues, or social comments.
musistudio/claude-code-router is tracked as a TypeScript project in the AI Agent area. This evaluation combines public GitHub metadata, category signals, short source summaries, and Git-Stars editorial rules rather than copying project documentation.
Momentum check: the repository has 36k total stars, with +0 today, +260 this week, and +0 this month. These growth windows help distinguish durable adoption from short-lived visibility spikes.
Maintenance check: current activity is Active; the latest push was 25 days ago, and the open issue queue is 1.0k, about 2.86% of total stars. Treat this as an adoption signal, not a substitute for engineering due diligence.
Adoption check: 3.0k forks and 36k watchers suggest how often the project is reused or followed. License signal: MIT. Always verify license compatibility before commercial or internal use.
Practical fit: this project is most relevant when you need TypeScript teams evaluating ecosystem-native tooling. Be cautious when you need a legal review, security audit, or production SLA.
Source check: Git-Stars currently has 2 explicit source reference(s) for this report and a recent growth signal of 260. Follow the original GitHub repository for final install, security, and release information.
Analysis
ReadyOriginal problem, capability, and verdict guidance are available.
Sources
ReadyRepository metadata and README/source references are attached.
License
ReadyMIT is recorded for review.
Maintenance
ReadyRecent activity is visible in repository metadata.
Alternatives
ReadyEnough nearby projects exist for comparison.
Momentum
36k Stars
Reuse
3.0k Forks
Attention
36k Watchers
Maintenance
active
License
MIT
Open issues
1.0k
Claude Code Router (CCR) is a local model gateway and control plane for coding agents. It provides one stable local endpoint for multiple agents like Claude Code, Codex, and Grok CLI, while allowing users to manage providers, models, accounts, routing rules, and tools from a single app.
Key Features
- Route, fail over, extend, and observe every request from one app - Supports multiple agents and providers with retries, credential pools, key rotation, and ordered fallback models - Adds capabilities like Fusion vision, web search, MCP tools, and ToolHub to existing models
AI Agent
Agent frameworks, autonomous workflows, and tool-use systems
Download the desktop app from the GitHub releases page.80
Health Score
Active
Commit Activity
Feb 25, 2025
Created
Jul 28, 2026
Last push
+39
Today's growth
+39
7-day growth
+39
30-day growth
Forks
Open
Watchers
musistudio
GitHub profileobra/superpowers
An agentic skills framework & software development methodology that works.
affaan-m/ECC
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
NousResearch/hermes-agent
The agent that grows with you
mattpocock/skills
Skills for Real Engineers. Straight from my .agents directory.
anomalyco/opencode
The open source coding agent.
✓
License
✓
Forked
✓ Active
Maintained
Problem Solved
CCR solves the fragmentation of managing separate model configurations for each coding agent (e.g., Claude Code, Codex, Grok CLI) by centralizing provider management, routing, and observability. It eliminates the need to repeatedly edit agent config files when switching models or providers, and adds resilience through retries, credential pools, and fallback models.
Capabilities
Developers can build multi-agent workflows that route requests across different models and providers, fuse capabilities like vision and web search into existing agents, orchestrate MCP tools and ToolHub, and monitor all activity through request logs, latency, token usage, and cost estimates. Real-world use cases include failover between Anthropic and OpenAI models, pooling API keys for rate limit avoidance, and extending Claude Code with custom tools without modifying its configuration.
Bottom Line
CCR is ideal for developers and teams who use multiple coding agents and want a unified control plane to manage providers, routing, and observability without per-agent configuration overhead. It should be avoided by those who only use a single agent/provider and don't need advanced routing or failover. The key trade-off is added complexity of running a local gateway versus the flexibility and resilience it provides.