claude-code-router

Claude Code Router (CCR) is a local model gateway and control plane for coding agents. Rather than configuring each client separately, it exposes one stable local endpoint (by default http://127.0.0.1:3456) and lets you manage the providers, models, accounts, routing rules and tools behind it from a single place. Supported agents include Claude Code, Claude Design, Codex, Grok CLI, Kimi CLI, Kilo Code, OpenCode, Pi, ZCode and WorkBuddy, plus compatible API clients. On the provider side it lists support for OpenAI Chat/Responses, Anthropic Messages, Gemini Generate Content/Interactions, OpenRouter, DeepSeek, SiliconFlow, Moonshot, Kimi Code, Mistral, Z.AI, Bailian and custom compatible endpoints. Core capability areas described in the README: - Agents: profiles with model overrides, scopes, environment settings, CLI and app launch entries, and multi-instance workflows. - Providers: built-in presets and custom endpoints, protocol probing, model discovery, connectivity checks, local login import where supported, single keys and credential pools. - Models and routing: searchable catalog, model descriptions for task selection, conditions on headers and bodies, prefixes, rewrites, retries and ordered fallbacks. - Tools and extensions: Fusion models, ToolHub, built-in browser automation, Chrome login-state import, wrapper and core gateway plugins, local routes and virtual models. - Access and quotas: separate CCR client keys with expiration and local request, token and image limits. - Observability: request and response details, resolved provider/model/credential, status, latency, tokens, estimated cost, tool calls and agent traces. - AgentClaw: agent relay through Weixin iLink, WeCom, Slack, Discord, Telegram, LINE, Feishu and DingTalk. Deployment options: a desktop app for macOS (Apple Silicon and Intel), Windows and Linux; an npm CLI requiring Node.js 22 or newer that starts the same gateway plus a browser-based management UI on port 3458; and a Docker Compose path. Desktop builds are produced with npm scripts, with Windows packaging requiring Windows x64 due to the native better-sqlite3 Electron module. The documented quick-start flow is: add a provider (preset or custom, with API key, protocol and models), start the server, apply an agent profile with a chosen model, then use the agent and inspect Logs to confirm the resolved provider, model, status, tokens, latency and errors. Routing conditions, retries, request rewrites and fallback models are configured in the Routing section. Full documentation is hosted at ccrdesk.top.