A Go CLI proxy that routes Claude Code requests through multiple upstream providers (OpenCode Go, OpenCode Zen, AWS Bedrock, OpenRouter, and Anthropic) with automatic model selection, format transformation, and fallback chains. It transparently intercepts Anthropic API calls and forwards them to your configured providers without requiring patches or modifications to Claude Code.
route Claude Code requests through multiple upstream providers (OpenCode Go, OpenCode Zen, and AWS Bedrock) with automatic model selection and format transformation.
README
routatic-proxy
Supported Providers
| Provider | Description | Best For |
|---|---|---|
| OpenCode Go | High-performance open-source coding models with flat-rate pricing | Daily coding, complex reasoning, cost-effective workloads |
| OpenCode Zen | Curated, tested models with pay-as-you-go pricing | Claude/GPT/Gemini access without multiple API keys |
| AWS Bedrock | Enterprise-grade models on your own AWS infrastructure | Enterprises needing data sovereignty and compliance |
| OpenRouter | Unified API for 100+ LLMs with automatic failover | Experimenting with models from multiple providers |
| Anthropic | Native Claude models with anthropic-first failover mode | Claude-first workflows with OpenCode fallback |
A Go CLI proxy that lets you route Claude Code requests through multiple upstream providers with automatic model selection and format transformation.
routatic-proxy sits between Claude Code and your chosen providers, intercepting Anthropic API requests, transforming them to the appropriate format (OpenAI, Anthropic, Responses, or Gemini), and forwarding them upstream. Claude Code thinks it's talking to Anthropic — but your requests go to the models and providers you configure.
oc-go-cc remains available as a compatibility alias, and existing OC_GO_CC_* environment variables and ~/.config/oc-go-cc/config.json files are still recognized.
Why?
OpenCode Go gives you access to powerful open coding models for $5/month (then $10/month). OpenCode Zen provides curated, tested models with pay-as-you-go pricing. AWS Bedrock lets you run models on your own AWS infrastructure. OpenRouter gives you unified access to 100+ models. This proxy makes all of them work seamlessly with Claude Code's interface — no patches, no forks, just set two environment variables and go.
Features
- Multi-Provider — Route through OpenCode Go, OpenCode Zen, AWS Bedrock, or OpenRouter from a single config
- Transparent Proxy — Claude Code sends Anthropic-format requests, proxy transforms to provider-native format and back
- Model Routing — Automatically routes to different models based on context (default, thinking, long context, background)
- Streaming Scenario Routing — Configurable routing for streaming requests (see CONFIGURATION.md)
- Fallback Chains — If a model fails, automatically tries the next one in your configured chain
- Anthropic-First Failover — Keep Claude on Anthropic and use OpenCode only during rate limits or outages
- Circuit Breaker — Tracks model health and skips failing models to avoid latency spikes
- Real-time Streaming — Full SSE streaming with live format transformation
- Tool Calling — Proper Anthropic tool_use/tool_result ↔ OpenAI/Gemini function calling translation
- Hot Reload — Watch config file for changes and reload automatically
- Self-Update — Check and install the latest release with one command
See docs/architecture.md for system design and request flow details.
GUI Version
This repository provides a cross-platform GUI for routatic-proxy:
- macOS — Native Cocoa window with system tray integration (requires CGO). Download the
.dmgfrom the Releases page. - Linux — Browser-based GUI via
xdg-open(default, no CGO required). For system tray: build withCGO_ENABLED=1and installlibappindicator-gtk3-devel(Fedora) orlibayatana-appindicator3-dev(Ubuntu/Debian). - Windows — GUI not supported (CLI only).
Dashboard tabs: Overview (real-time metrics & model distribution), History (last 1000 requests with filters), Settings (edit config with hot-reload).
routatic-proxy ui
On macOS, this opens a native window. On Linux, it opens your default browser.
Quick Start
# 1. Install
brew tap routatic/tap && brew install routatic-proxy
# 2. Initialize configuration
routatic-proxy init
# 3. Set your API key
export ROUTATIC_PROXY_API_KEY=sk-opencode-your-key-here
# 4. Start the proxy
routatic-proxy serve
# 5. Configure Claude Code
export ANTHROPIC_BASE_URL=http://127.0.0.1:3456
export ANTHROPIC_AUTH_TOKEN=unused
# 6. Run Claude Code
claude
Fedora / RHEL: each release ships x86_64 and aarch64 RPMs —
sudo dnf install https://github.com/routatic/proxy/releases/download/vX.Y.Z/routatic-proxy-X.Y.Z-1.x86_64.rpm.
See docs/fedora-setup.md for package contents and the systemd user service.
See INSTALLATION.md for Homebrew, Scoop, Docker, and build-from-source options.
Prefer a GUI for switching providers? routatic-proxy works with CC-Switch — see Using with CC-Switch.
CLI Commands
routatic-proxy serve Start the proxy server
routatic-proxy serve -b Start in background (detached from terminal)
routatic-proxy stop Stop the running proxy server
routatic-proxy status Check if the proxy is running
routatic-proxy init Create default configuration file
routatic-proxy validate Validate configuration file
routatic-proxy models List all available models
routatic-proxy ui Launch the GUI dashboard
routatic-proxy autostart enable Enable auto-start on login
routatic-proxy update Update to the latest release on your channel
routatic-proxy update check Check for a newer release without installing
routatic-proxy update-channel Show or switch release channel (stable|beta)
routatic-proxy --version Show version
Documentation
| Document | Description |
|---|---|
| MODELS.md | Model reference across all providers — capabilities, costs, endpoints, routing recommendations |
| docs/openrouter.md | OpenRouter provider setup and configuration |
| CONFIGURATION.md | Config file reference, env vars, model routing, fallback chains |
| INSTALLATION.md | Homebrew, Scoop, build from source, Docker |
| CONTRIBUTING.md | Development setup, architecture |
| TROUBLESHOOTING.md | Common issues and debug mode |
| docs/architecture.md | System design and request flow |
| docs/fedora-setup.md | Fedora 44 setup (systemd, SELinux) |
| docs/reference-api.md | HTTP API reference |
| docs/howto-add-model.md | Adding new models (zero code changes) |
| docs/howto-custom-routing.md | Customizing scenario detection and routing |
| docs/howto-debug-routing.md | Debugging routing issues |
Release Channels
This project ships on two channels. Stable is the default; beta gets you the newest features early.
routatic-proxy update-channel beta # opt in to betas
routatic-proxy update # install the newest beta
routatic-proxy update-channel stable # back to stable releases
See Beta Releases for the full walkthrough (Docker beta tag, installing a specific prerelease, returning to a stable build) and RELEASE_PROCESS.md for how releases are built.
Beta Channel (Automatic)
- Trigger: Every push to
mainbranch - Version format:
v{UPCOMING}-beta.{N}(e.g.,v0.6.4-beta.1), where{N}is a sequential counter that restarts once that version ships as stable - GitHub release: Marked as prerelease
- Docker tags:
beta(rolling), plus the exactv{UPCOMING}-beta.{N} - Use case: Get the latest features and bug fixes immediately; ideal for testing
Production Channel (Manual)
- Trigger: Manual
workflow_dispatchonreleasesbranch - Version format:
vX.Y.Z(semantic versioning) - GitHub release: Marked as stable
- Docker tags:
vX.Y.Z,vX.Y,vX,latest - Use case: Stable, tested releases for production use
Contributing
We welcome contributions! Please see CONTRIBUTING.md for development setup, architecture overview, and how to submit pull requests.
License
Comments (0)
Sign in to join the discussion.
No comments yet
Be the first to share your take.