Local LLM gatewayOpen source · MITmacOS / Linux / Windows
Keep the tools you love. Bring every provider, key and account together.
Clipal connects Claude Code, Codex CLI, OpenCode and 15 more AI coding CLIs to one local LLM gateway and API proxy. Manage API keys and OAuth accounts, rotate keys and fail over past 429 rate limits, and track requests, tokens and costs in your browser.
Providers, takeover and status. In one local view.
Upstream credentials, CLI configuration and gateway health belong in the same workspace. Clipal brings them together in a local browser console at 127.0.0.1:3333.
127.0.0.1:3333
Providers, usage and spend — side by side.
Manage API-key and OAuth providers in one view, switch between automatic failover and manual pinning, and inspect per-provider token usage and spend.Product screenshot · example configuration
127.0.0.1:3333
Preview and roll back CLI configs.
Preview targeted configuration changes, apply them with a saved baseline, and roll back when you need to.Product screenshot · example configuration
127.0.0.1:3333
Gateway health and live routes at a glance.
Verify service readiness, uptime, circuit breaker activity and the active route for each protocol family from one status screen.Product screenshot · example configuration
127.0.0.1:3333
Listen boundaries, circuit breakers and sticky sessions.
Tune listen boundaries, circuit breakers and sticky session behavior in the browser. By default, the management UI only accepts local loopback connections.Product screenshot · example configuration
02Features
API keys, OAuth and failover. Under local control.
One place to set up every coding CLI and upstream account, so you can stay focused on the code.
CLI takeover
Preview, back up and roll back CLI configs.
Connect your tools through CLI takeover. Review targeted user-level config diffs first; Clipal saves the managed files’ original baseline so you can always return to it.
After shell integration changes, open a new terminal. Project, session or environment settings can still override a tool’s configuration.
Auto failover
Multi-key rotation and 429 provider failover.
In auto mode, Clipal rotates to the next available API key on the current provider, cools down rate-limited routes on 429 errors, falls back to another compatible provider, and reuses working routes with sticky sessions. Prefer a fixed route? Pin a provider in manual mode.
Illustrative sequence
Provider A
key_01Selected
key_02Standby
Provider B
key_01Standby
01 / Start with the selected provider and key.
02 / If needed, try the next available key on that provider.
03 / Then try another compatible provider.
Manual mode stays pinned; it does not switch keys or providers automatically.
Native protocols
Native Anthropic, OpenAI and Gemini routes.
One local entry point, /clipal/*. Preserves native request formats and routes by path — plus OpenAI-compatible upstreams and desktop clients — without guesswork protocol translation.
Anthropic Messages
OpenAI Chat · Responses
Gemini generateContent
OAuth accounts
Multi-account OAuth for Claude, Codex and Google.
Connect Claude, Codex and Antigravity-backed Google accounts alongside API keys. Credentials with refresh tokens refresh automatically.
ClaudeCodexAntigravity
Account and upstream eligibility still apply.
Usage & cost
Request, token and cost tracking with sources.
Use upstream-reported costs when available; otherwise, the embedded exact-model pricing catalog. Unknown prices stay unknown.
Upstream-reportedPreferred source
Model catalogFallback estimate
Unknown priceLeft unpriced
Catalog estimates are not your provider’s invoice.
03Integrations
Works with 18 AI coding CLIs. Keep your favorites.
One place to preview, apply and roll back their connection settings.
Manages user-level configs (such as ~/.claude/settings.json, ~/.codex/config.toml, opencode.json and .aider.conf.yml) and also supports OpenAI-compatible desktop apps like Cherry Studio and Chatbox. Support scope varies by client; configuration writes alone do not verify live runtime traffic.
04Install
Install. Start. Open localhost.
Install Clipal, start the gateway, and add your first provider. A single native binary for macOS, Linux and Windows; the console runs in your browser.
Once Clipal is running on your machine, open the console to add an API-key provider or OAuth account, then preview and enable CLI takeover.
Let your AI assistant handle the setup +
Copy this prompt into a terminal-capable coding assistant.
Please help me install and launch Clipal, the local LLM gateway. Official repository: https://github.com/PAIArtCom/Clipal
1. Identify my operating system and check whether npm is available. Prefer: npm install -g clipal
2. If npm is unavailable, use the official installer for my platform:
macOS/Linux: curl -fsSL https://clipal.paiart.com/install.sh | sh
Windows PowerShell: powershell -ExecutionPolicy ByPass -c "irm https://clipal.paiart.com/install.ps1 | iex"
3. Install and start Clipal in the background with: clipal service install (it registers the OS background service, starts Clipal immediately, and waits for the health check; fall back to foreground clipal only if background services are unavailable). Confirm that http://127.0.0.1:3333/ is reachable.
4. Guide me through adding my first provider or OAuth account in the Web UI, previewing CLI takeover changes, and applying them. Explain when I need to open a new terminal and how to roll back.
05FAQ
Local gateway, clear boundaries.
Can I combine OAuth accounts (Claude, Codex, Antigravity) with pay-as-you-go API keys? +
Yes. Add API-key providers and supported OAuth accounts to the same channel group. In auto mode, Clipal tries available keys on the current provider first, falls back across compatible API-key or OAuth providers when rate-limited, and reuses working routes for matching follow-up requests. You can also pin a single provider in manual mode.
Does “local” mean my AI requests stay on my machine? +
No. Clipal runs the gateway and management console locally, but sends API requests and necessary authentication information to the upstream providers you choose. It is not offline inference. By default, the management UI only accepts loopback connections; remote UI and proxy listening boundaries can be configured separately.
Where does Clipal keep configuration and credentials? +
API-key providers are stored in YAML under ~/.clipal. OAuth credentials live separately in ~/.clipal/oauth/. Protect those files with appropriate permissions on your machine; Clipal does not promise that all stored credentials are encrypted.
What does rolling back CLI takeover restore? +
Rollback restores the managed files to the original backup from the start of the current takeover cycle. Reapplying keeps that same backup. Project, session, and environment settings may still override the tool’s connection settings; open a new terminal after shell integration changes.
Does Clipal translate between model protocols? +
Clipal preserves the native Anthropic, OpenAI, and Gemini request families and routes by request path through /clipal/*. Use an upstream compatible with the protocol your tool sends; this is not arbitrary protocol conversion.
How should I read the cost figures? +
Clipal prefers upstream-reported cost. If that is unavailable, it uses the embedded pricing catalog for exact model matches. Unknown pricing is left missing, and catalog updates do not recalculate historical costs. Catalog-based figures are estimates, not a billing guarantee.
How do I roll back CLI changes or uninstall Clipal cleanly? +
Use Rollback in the CLI Takeover tab to restore managed files to their pre-takeover backup. If you installed the background service, run clipal service uninstall, then remove the binary (for example npm uninstall -g clipal) and delete ~/.clipal when you no longer need saved settings or usage history.
A local tool. A shared project.
Read the code. Share an idea. Help make everyday AI tooling easier to live with.