Native support for OpenRouter, new-api, and any provider. Automatically patches ~/.claude/settings.json and standard configs—eliminating 429 rate limits through intelligent multi-key rotation and failover.
Directly patches ~/.claude/settings.json & ~/.codex/config.toml.
Clipal also serves as a unified proxy for Coding Agents such as Claude code, Codex, Gemini CLI, Aider,
Continue ...,
and AI Apps such as Jan, Cherry Studio, Chatbox, and any app supporting custom API endpoints (OpenRouter,
new-api, sub2api).
Supported Protocols
CLI Tools & AI LLM Applications
Three things that make Clipal the only LLM proxy worth running.
Stop hunting for hidden config files. Clipal
natively patches ~/.claude/settings.json and standard configuration files, transforming
into a zero-configuration local reverse proxy for Claude Code, AI CLI tools, and Desktop apps without
env-var pollution.
Conquer strict 3rd-party API rate limits. Clipal manages shared token pools, instantly detecting 429 errors to gracefully rotate keys or failover to backup providers—all while preserving your contextual session state.
Unlike heavy Python proxies (like LiteLLM) or complex Docker deployments, Clipal is a high-performance, zero-dependency API Gateway compiled in Go for macOS, Linux, and Windows. Download. Executable. Proxy active.
How we engineer stability: zero config loss, zero auth loops, and unified token pools.
Beyond simple proxying — Clipal is the infrastructure that cc-switch and ccNexus users have been waiting for.
| Feature / Tool | cc-switch | ccNexus | Clipal |
|---|---|---|---|
| Binary-only (No Docker) | ✗ (Script) | ✓ | ✓ |
| Claude / Codex / Gemini Takeover | Limited | ✓ | Unified |
| API Provider Multi-key Pools | ✗ | ✓ | Bulletproof |
| Universal Base-url Support | ✓ | ✓ | ✓ (w/ Metrics) |
| Non-destructive Config Merge | ✗ (Overwrites) | ✓ | ✓ (Safeguarded) |
| Protocol Auth Emulation | Limited | ✗ | ✓ (No Loops) |
| Real-time Flow Monitoring | ✗ (Blackbox) | ✓ | ✓ (One-click) |
Directly hijacking ANTHROPIC_BASE_URL without environment
pollution. Perfect for relaying requests to Bedrock, Vertex AI, or any 3rd-party Claude Mirror without
protocol header errors.
Distribute requests across multiple Google Gemini API keys. Automatically fallback to Flash models via weighted pools when Pro quotas hit their ceiling.
Choose your preferred installation method.
Copy this prompt and paste it into Claude
Code, Aider, or Goose — it will handle the entire binary
installation and PATH setup for you:
Please help me install and start Clipal. Project: https://github.com/lansespirit/Clipal Please detect my current OS and architecture, check the project's Releases and docs, and complete the download, installation, and startup for me. Then confirm that I can open the Web UI successfully. Use these official links when needed: - Releases: https://github.com/lansespirit/Clipal/releases - Getting Started: https://github.com/lansespirit/Clipal/blob/main/docs/en/getting-started.md - Web UI Guide: https://github.com/lansespirit/Clipal/blob/main/docs/en/web-ui.md After that, guide me through using the Web UI to enable CLI takeover and add my first provider.
Visit http://127.0.0.1:3333 to add
your API keys, apply CLI Takeover, and manage providers.
Neither. Clipal is a standalone local binary. Your API
keys are stored in an encrypted config.json on your own machine. Zero cloud storage, zero
data leakage.
Yes. Clipal natively supports OpenAI-compatible, Anthropic Claude, and Google Gemini protocols. You can route your Claude Code terminal, OpenAI-powered Codex, and Gemini CLI traffic through any third-party provider or local endpoint effortlessly.
Clipal provides a multi-dimensional reliability layer. Beyond single-provider multi-key rotation, it supports multi-provider concurrency and intelligent sticky sessions. If your primary OpenRouter key hits a rate limit, Clipal instantly diverts to another key or provider while ensuring your session context remains consistent.
In fact, it makes it more stable. For Codex/OpenCode, Clipal uses a
standardized model_provider = "clipal" configuration. Unlike other proxies that force
provider changes (which resets history), Clipal keeps the provider constant while swapping the underlying
endpoints in the background, preserving all your context and history.
While cc-switch manages multiple configs, Clipal is a
high-performance gateway that supports complex multi-key token pools, deep config
injection for settings.json, and real-time observability.
Yes. Most proxies break when talking to Bedrock/Vertex via Claude Code due to header strictness. Clipal provides native protocol emulation to fix these issues at the socket level.
Negligible. Written in Go, Clipal processes requests in microseconds. It consumes less than 50MB of RAM, far more efficient than Node.js or Python-based proxies.
Unlike other tools that overwrite your settings, Clipal uses a
non-destructive AST-merging strategy to patch settings.json. We only update necessary
fields and preserve your
enabledPlugins, custom environment variables, and manual tweaks.
Yes. Most Login Loops are caused by incorrect header handling when proxying. Clipal's protocol emulation layer ensures headers are properly scrubbed and injected, keeping your session stable without repeated authentication prompts.
Clipal provides a real-time observability dashboard. You can see the full request flow, response times, and error codes in one click. If a request fails, we'll tell you exactly if it was a network timeout or an invalid key.
Get setup help, share configs, and discuss new providers with other developers.
Scan to join WeChat group