routatic-proxy CLI
Local CLI proxy for Claude Code that translates provider API formats and selects models using configurable routing rules
- 979 ★ on the repository
- Last commit
- AGPL-3.0
Extended access
Why this level
- The proxy processes client code and messages with provider API credentials
- Fallback routing may send context to another provider and consume its paid API access
Install
- Works in
Manual install
brew tap routatic/tap
brew install routatic-proxyInstallation for macOS and Linux. Run `routatic-proxy init` afterward; provider API access is configured separately.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The proxy processes client code and messages with provider API credentials
- Fallback routing may send context to another provider and consume its paid API access
This is third-party code. Review the repository files before installing.
What it does
routatic-proxy receives Claude Code requests and forwards them to configured model providers. It translates message and tool-call formats between supported APIs. Claude Code remains the interface while a selected provider's model produces the response. You assign models to request types and set the order of fallback connections in the configuration. A failed primary call can move to another configured option. Rules can be changed without repeatedly restarting the service. The CLI starts either the proxy alone or a proxy with a dashboard. `validate` and `models` check the settings and list model catalog entries. You can use OpenCode Go and OpenCode Zen APIs. Those services, AWS Bedrock and OpenRouter require your own credentials.
Who it is for. For developers who want one local configuration to manage several model providers used by Claude Code.
Good fit when
- Route different task types to predefined models
- Configure fallback providers for individual API failures
- Validate settings and inspect proxy status before use
- Manage provider settings centrally for several client runs
Not a fit when
- Your organization permits only a direct client connection to one provider
- You need identical responses and tool behavior from every connected model
- You expect the software to include access to providers you have not configured
Example request
Prepare routatic-proxy for my model APIs. Show the routing configuration, validate it and keep the service local. I will enter the keys myself.Limitations
Each provider needs its own credentials and API access; proxy installation does not supply a model. Changing models can affect answers and tool calls, while switching after a stream starts can repeat text already received. The proxy receives credentials and request contents; rerouting can send the same code to another operator. The built-in updater replaces its binary without confirmation or checksum verification; update managed installations through their package manager.
How to disable. Run `routatic-proxy stop`, remove the proxy endpoint from Claude Code configuration and restore the desired client connection. Disable autostart separately if enabled. Remove the package through its installation method.
FAQ
How does `start` differ from `serve`?
`routatic-proxy start` also opens a dashboard. `routatic-proxy serve` runs only the proxy. Both support a background flag.
Where do the local services listen?
The proxy defaults to `127.0.0.1:3456` and the dashboard to `127.0.0.1:3445`. You can change the proxy binding and port. The dashboard runs in `start` mode.
How do I point Claude Code at the local proxy?
After starting the proxy, run `export ANTHROPIC_BASE_URL=http://127.0.0.1:3456` and `export ANTHROPIC_AUTH_TOKEN=unused` in the terminal where you then launch `claude`. This is the default local-port example. `unused` is a placeholder; configure the real provider key in the proxy.
Can I retain the client's requested model?
Yes. `respect_requested_model` honors the model name sent by Claude Code. `model_overrides` maps particular client names to configured upstream models.
How should managed installations be updated?
Use the package manager, such as `brew upgrade routatic-proxy`. The built-in updater is for standalone binaries. RPM and Docker installations have their own update paths.
Can I expose the proxy to other machines?
Configure the listening address and incoming-request checks first. A local default does not secure a remote configuration. The code uses AGPL-3.0.
Discussion
No questions or reviews yet.
Related
CLI toolsA local gateway for Claude Code, Codex, OpenCode and other agents: pick model providers, route requests, set fallbacks and read logs
CCS
CCS - Claude Codex Switch
A CLI that switches Claude Code between accounts, providers and local models without editing configs
The brick CLI runs a local model router in front of Claude Code or Codex and sends each request to a fitting model.
A Go CLI that switches Claude Code profiles with one command, swapping settings, CLAUDE.md and MCP servers together with a backup.
A Claude Code plugin that asks several AI models the same question and shows their answers side by side with a synthesis of agreement and divergence
A CLI that plugs third-party models into Claude Code orchestration: workflows, agent teams and subagents on DeepSeek, GLM, Kimi, Qwen or a Codex subscription
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| routatic-proxy (this card) | no | 979 | |
| CC Switch | no | 151,986 | switches provider settings through a GUI; routatic-proxy handles requests and fallback routing itself |
| LLMstudio | no | 390 | The CLI starts a language-model proxy and a request tracking service for debugging applications across model providers. |
README in short
Existing installations retain the `oc-go-cc` alias and legacy environment variables. Distribution includes Homebrew, Scoop and Docker. The graphical wrapper and background service use the same proxy.