cliproxy-rs

Use DeepSeek, GLM, Kimi, OpenRouter and more in Codex CLI and Claude Code: one local endpoint, API translation, failover. Single Rust binary, CLIProxyAPI-compatible.

• API translation. Codex CLI sends Responses requests, and the proxy sends Chat Completions to providers that only offer those, tool calls included. Claude Code's Messages requests are translated to the selected provider's format the same way.
• Several keys and providers behind one model name. By default, a 429 cools that key for the model and the request moves to another ready key or provider with the same alias.
• One binary with the dashboard built in. It reads CLIProxyAPI's config.yaml and credential files. Parity with CLIProxyAPI v8.0.35 is partial; PARITY.md has the counts.

curl -fsSL https://raw.githubusercontent.com/vayungodara/cliproxy-rs/master/install.sh | sh

On Windows, or with Homebrew or Scoop, see Quick start.

New in 0.4.0: config files load the way CLIProxyAPI's YAML library reads them, streams that end early fail the way CLIProxyAPI fails them, and the Antigravity, Gemini, Vertex, Codex and xAI providers follow CLIProxyAPI v8.0.35 more closely. Codex clients can use tool search on the Responses routes. Some configs load differently or no longer load, so read "Before you upgrade" in the release notes first.

Set it up with your coding agent. Paste this into Claude Code, Codex or Amp on the machine where the proxy should run:

Install cliproxy-rs on this machine by following https://github.com/vayungodara/cliproxy-rs/blob/master/docs/AI-SETUP.md

Quick start

1. On macOS or Linux:

   curl -fsSL https://raw.githubusercontent.com/vayungodara/cliproxy-rs/master/install.sh | sh
   

   On Windows, in PowerShell:

   irm https://raw.githubusercontent.com/vayungodara/cliproxy-rs/master/install.ps1 | iex
   

   The installer checks the release checksum, writes ~/.cliproxy-rs/config.yaml, starts the proxy and opens the dashboard. On Windows, the config is %USERPROFILE%\.cliproxy-rs\config.yaml. It saves new keys in keys.env without printing them.

   Other ways to install: Homebrew on macOS or Linux, Scoop on Windows, and the rest in INSTALL.md.

2. Sign in to the dashboard with CLIPROXY_MANAGEMENT_KEY from the keys.env next to your config. Add a provider API key, or connect your own account. Read Accounts and provider terms before connecting a subscription.

3. Open the dashboard's Use with tools page and copy the Codex CLI or Claude Code settings. Your tools use CLIPROXY_CLIENT_KEY, not the management key.

Run the install command again to upgrade, or brew upgrade cliproxy-rs with Homebrew. Both keep your config and keys. INSTALL.md covers start at login, release binaries, Docker and building from source. GETTING-STARTED.md has the longer walkthrough.

What is this?

cliproxy-rs is a Rust rewrite of CLIProxyAPI. It reads the same config.yaml and credential formats and implements the client routes and v8 Management API. The dashboard shows accounts, provider limits, request history and tool settings.

The compatibility target is CLIProxyAPI v8.0.35. Parity is incomplete: the audit has 1,951 items, with 1,053 covered, 872 partial and 26 missing. PARITY.md defines those counts.

How it compares

Checked against each project's own README on 28 October 2026.

¹ Not stated in CLIProxyAPI's README; checked in its v8.0.35 source and release assets. cliproxy-rs's translation and failover are ports of that code.

Where the others are stronger:

• CLIProxyAPI is the complete implementation that cliproxy-rs follows. It was faster in the synthetic runs under Performance, and its README lists many apps built on it.
• LiteLLM covers 100+ providers and adds virtual keys, spend tracking, guardrails and a Python SDK.
• claude-code-router has routing conditions on headers and bodies, ordered fallback models, its own client keys with request and token limits, and a desktop app.
• opencodex supports 40+ providers out of the box, also serves Claude Desktop and Grok Build, and has a desktop app.

Use it with your tools

The local OpenAI base URL is http://127.0.0.1:8317/v1. Claude Code and Gemini clients use http://127.0.0.1:8317 without /v1. Use your installation's port and client key.

CLIENTS.md has client settings, including GPT in Claude Code. Not every model and tool combination has been tested.

API keys: Codex CLI and mixed providers

Codex CLI only speaks the Responses API now. A provider entry with wire_api = "chat" stops Codex with "wire_api = "chat" is no longer supported".

If you only use one provider and it serves the Responses API, Codex can talk to it directly. DeepSeek's API, Z.ai's GLM Coding Plan and Kimi Code do, and each publishes its own Codex setup: DeepSeek, GLM Coding Plan, Kimi Code.

The proxy is for the rest: an endpoint that only offers Chat Completions, such as OpenCode Go's models, or several providers and keys behind one endpoint, with failover when one returns 429. It accepts Responses requests from Codex and sends Chat Completions upstream, tool calls included.

You do not need a subscription login. Merge this provider block into ~/.cliproxy-rs/config.yaml, or %USERPROFILE%\.cliproxy-rs\config.yaml on Windows. Keep access.api-keys, management.secret-key and the rest of your config. The proxy reloads the configuration on save. The upstream keys below are separate from your proxy's client key. Replace the key and upstream model placeholders with values from each provider.

api-keys:
  openai-compatibility:
    - name: deepseek
      base-url: "https://api.deepseek.com"
      keys:
        - api-key: "<deepseek-api-key>"
      models:
        - name: "<deepseek-model-id>"
          alias: "deepseek"
    - name: openrouter
      base-url: "https://openrouter.ai/api/v1"
      keys:
        - api-key: "<openrouter-api-key>"
      models:
        - name: "<openrouter-model-id>"
          alias: "router"

Use the same structure for any of these metered APIs. The base URL excludes /chat/completions; the proxy adds it.

Put this in ~/.codex/config.toml:

model = "deepseek"
model_provider = "cliproxy"

[model_providers.cliproxy]
name = "cliproxy-rs"
base_url = "http://127.0.0.1:8317/v1"
env_key = "CLIPROXY_CLIENT_KEY"
wire_api = "responses"

export CLIPROXY_CLIENT_KEY=your-client-key
codex

Use the port and CLIPROXY_CLIENT_KEY from your installation's keys.env. Codex CLI sends Responses requests to the proxy; the proxy translates them to Chat Completions for these ups