Discofork
Repository brief

musistudio/claude-code-router

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-31T09:59:55.071Z
1mo ago

musistudio/claude-code-router

musistudio/claude-code-router is a popular, actively maintained Node.js/TypeScript project for routing Claude Code requests to different model providers and customizing requests/responses. It is MIT licensed, not archived, and has substantial adoption with 30,814 stars and 2,384 forks. The repository includes a CLI, server, UI, docs site, examples, scripts, and a plugin-oriented setup, which makes it a plausible fork target for teams that want to change routing behavior, provider support, or integrations.

GitHub
Loading tags...
Stars30,814
Forks2,384
Default branchmain
Last pushed2026-03-04T05:48:17Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork if you want a more guided, operator-friendly CCR with better provider setup and background execution. Prefer upstream if you want the newest router behavior, latest provider/model updates, and the most actively maintained codebase.

Prefer upstream unless you specifically want this exact frozen snapshot as a starting point; this fork adds no documented capabilities and appears behind by 50 commits.

Prefer upstream unless you specifically need this fork's repo identity; this fork adds no visible features and is significantly behind.

Prefer this fork if you want GPT-5-specific experimentation, quickstart automation, and a repo that seems tuned for debugging router behavior. Prefer upstream if you want the latest broadly maintained router features, cleaner release flow, and lower merge risk.

Prefer this fork if you want a more opinionated, CLI-centered router with unified rules, better logging, migration help, and GLM-specific workflows. Prefer upstream if you want the broader, more current feature set and lower upgrade risk.

Prefer upstream unless you specifically need this exact historical snapshot. This fork adds no visible value yet carries the maintenance risk of being 171 commits behind.

Prefer upstream unless you specifically need this older snapshot; the fork adds no visible functionality and is materially behind.

Prefer upstream unless you specifically need this fork as a starting point for private work; it shows no unique capabilities and is materially behind current upstream.

Choose this fork if you want upstream Claude Code Router behavior and only need Hicap-specific documentation or support framing. Do not choose it for new routing features or platform changes.

Choose this fork if you want more than routing: it looks better for provider operations, testing, and custom workflows. Stay with upstream if you want the most stable, broadly supported baseline with less divergence risk.