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

LogoGit-Stars
Top StarsTrendingAI AgentsDaily PicksViral ReposInsights
LogoGit-Stars

Discover top GitHub projects with real rankings and AI insights

GitHub
Built withLogo of Git-StarsGit-Stars
Rankings
  • Top Stars
  • Trending
  • AI Agents
  • Daily Picks
  • Explore
Resources
  • Insights
  • Editorial Policy
About
  • About
  • Contact
Legal
  • Privacy Policy
  • Terms of Service
© 2026 Git-Stars. All Rights Reserved.
AI Agent Analysis
CR

musistudio/claude-code-router

One local control plane for every AI agent: route across models, fuse new capabilities, orchestrate tools, and stay fully in control.

stars
36k
Language
TypeScript
GitHub
Source and compliance noteLast synced: Jul 29, 2026

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.

Original GitHub sourceMethodologyEditorial Policy

Overview

Claude Code Router (CCR) is a local model gateway and control plane for coding agents that provides a single endpoint to manage multiple AI providers, models, routing rules, and tools, enabling seamless switching and failover without reconfiguring individual agents.

Installation

Download the desktop app from GitHub releases or run the quick start script from the repository.

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.

What you can build

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.

Community sentiment

Positive

No community feedback yet.

Concerns

No concerns documented yet.

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.

Analyzed by Git-Stars - 7/28/2026