Skip to content
Get packs

Guide · Open source

How to use CLIProxyAPI: clone, configure and point clients at it

Updated · written with AI from the project's own documentation and checked against our catalogue data

CLIProxyAPI is an open-source proxy server written in Go that presents accounts from several AI providers, including Claude Code, Codex, Gemini, Grok and Muse, through OpenAI, Gemini or Claude compatible interfaces. It is aimed at developers who already use tools that speak one of those formats and want to route them elsewhere. After this guide you will know what the project does, how to get the source, what the setup involves, and where it is a poor fit.

CLIProxyAPIrouter-for-me/CLIProxyAPI · ★ 57.3k · MIT

Quick start

  1. 1Clone the repository. Run git clone https://github.com/router-for-me/CLIProxyAPI to download the source.
  2. 2Read the docs in the repo. Check the cloned project's documentation for build steps, configuration file names and supported options.
  3. 3Add provider accounts. Log in or authorise the CLI accounts you hold, using the OAuth or login method each provider supports.
  4. 4Start the proxy. Run the service as described in the project's docs so it listens locally.
  5. 5Point your client at it. Set your OpenAI-, Gemini- or Claude-compatible tool's base URL to the local proxy address.
  6. 6Test a request. Send a simple prompt and confirm the response comes back through the proxy.

What CLIProxyAPI does

CLIProxyAPI sits between your client and the AI providers. Any tool or SDK that can talk to an OpenAI (including the Responses API), Gemini (including Interactions) or Claude compatible endpoint can send its requests to CLIProxyAPI instead of directly to the provider.

The README describes the goal as letting you use multiple CLI accounts locally through any compatible client or SDK. The providers listed in the README include Kimi, OpenAI GPT-6 models (including access through Codex OAuth), Anthropic Claude models, Google Gemini models (via Gemini API, AI Studio, Vertex AI, Gemini CLI and Antigravity accounts), xAI Grok models, Meta Muse models and Devin models.

  • Supported client formats: OpenAI (including Responses), Gemini (including Interactions), Claude, and Codex-style access.
  • Model availability varies by channel, according to the README.
  • Authentication options mentioned include OAuth and login flows such as Meta login and a Devin login flag.

Get the source code

The README's install instruction is to clone the repository. The project is MIT licensed and written in Go. The README does not list prerequisites, so check the repository for build or runtime requirements before you start.

git clone https://github.com/router-for-me/CLIProxyAPI

Configure your provider accounts

Setup is done through the command line and configuration files, so expect to edit config and log in each provider account you want to use. The README mentions OAuth and login options for several providers, and a Devin account is connected with the --devin-login flag. Read the configuration documentation in the cloned repository for exact file names and keys, because the README excerpt does not spell them out.

If you want a graphical configuration UI, the README points to a separate desktop client called EasyCLIProxyAPI, which offers automatic updates, system tray integration and one-click start/stop.

  • Add one or more CLI accounts, one per provider you intend to use.
  • Keep provider credentials on your own machine; the project is designed for local use.
  • Use the desktop client if you prefer a GUI over editing files.

Point your client at the local endpoint

Once the proxy is running, configure your existing OpenAI-, Gemini- or Claude-compatible tool to use the proxy's address as its base URL. The exact address and port depend on your configuration, so use the values from the repository docs rather than guessing.

Choose the model names the proxy exposes, such as the Claude, GPT, Gemini or Grok entries listed in the README. Some models are only available through particular accounts or channels.

Limits to weigh before you rely on it

The README does not guarantee uptime or official support. The project depends on third-party account access, and the README does not explain how provider accounts are authorised beyond OAuth and login options. Check each provider's terms of service before routing traffic this way.

Several sponsor sections in the README promote relay services. These are third-party commercial offers and are separate from the project itself; the README does not endorse them as part of the software.

  • No guaranteed uptime or support.
  • Provider terms-of-service risk is not addressed by the README.
  • Model lists change; the README itself notes availability varies by channel.

What people use it for

  • Routing an existing OpenAI-compatible coding tool to a Claude or Gemini model through one local endpoint.
  • Using several CLI accounts from one place instead of switching tools per provider.
  • Testing how a client behaves against different model families behind a single interface.
  • Experimenting with Muse, Grok or Devin models from a tool that only supports one API format.

Frequently asked questions

Is CLIProxyAPI free to use?

The project is released under the MIT licence, according to the repository summary. Provider accounts and any model usage are separate, so check the costs and terms of each provider you connect.

What do I need to install CLIProxyAPI?

The README lists no prerequisites. The install method is to clone the repository from GitHub and follow the project's documentation. Because the project is written in Go, you will need to check the repo for the build tooling it expects.

Does CLIProxyAPI have a graphical interface?

The core project is configured through the command line and config files. The README recommends a separate desktop client, EasyCLIProxyAPI, that adds a graphical configuration UI and one-click start and stop.

Which clients work with CLIProxyAPI?

Any client or SDK that speaks an OpenAI (including Responses), Gemini (including Interactions) or Claude compatible API should be able to send requests to it, according to the README.

How does CLIProxyAPI compare to LiteLLM, One API or New API?

The analysis lists LiteLLM, One API and New API as comparable projects. This guide does not benchmark them. Compare them on the features you need, such as which providers and client formats each supports.

Is CLIProxyAPI safe to use with my provider accounts?

The README does not guarantee uptime or official support and does not explain how provider accounts are authorised beyond OAuth and login options. Review each provider's terms of service before you use it.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

CLIProxyAPI suits developers who are comfortable with config files and a command-line server, and who want one local endpoint for several CLI accounts behind OpenAI, Gemini or Claude compatible tools. It is a poor fit for non-technical users who need a point-and-click app, or for anyone who needs guaranteed uptime, official support or certainty about provider terms. Pick a managed API gateway such as LiteLLM, One API or New API if you need a more established, supported route.

Install options & downloads