Devtoolwatch BoardCLIProxyAPI review
CLIProxyAPI is a Go proxy server that exposes CLI coding accounts like Codex, Claude Code and Gemini CLI through OpenAI, Gemini and Claude-compatible APIs.
TL;DR
CLIProxyAPI is a proxy server that turns CLI tool accounts such as Codex, Claude Code, Grok Build, Gemini CLI and Antigravity into OpenAI, Gemini, Claude or Codex-compatible API endpoints. It is for developers who want to call those models from any compatible client or SDK. It also supports multi-account round-robin load balancing and an embeddable Go SDK.
- 57.1kGitHub stars
- +1knew stars, week of Oct 25
- #6in Inference and training this week
CLIProxyAPI at a glance
- Category
- Inference and training
- Maintained by
- Router-For.ME (organization, @router-for-me on GitHub)
- License
- MIT
- Language
- Go, PowerShell, Shell
- Repository
- github.com/router-for-me/CLIProxyAPI
- Latest release
- v8.0.51 on GitHub, Nov 1, 2026
- First published
- Jul 1, 2025
What CLIProxyAPI does
- CLIProxyAPI provides OpenAI, Gemini, Claude, Codex and Grok-compatible API endpoints that any compatible client or SDK can call.
- CLIProxyAPI connects OpenAI Codex, Claude Code and Grok Build accounts through OAuth login.
- CLIProxyAPI balances requests across multiple accounts with round-robin load balancing for Gemini, OpenAI, Claude and Grok.
- CLIProxyAPI supports streaming, non-streaming and WebSocket responses where supported, plus function calling and text-and-image input.
- CLIProxyAPI can route to OpenAI-compatible upstream providers such as OpenRouter through its config.
- CLIProxyAPI also supports Kimi, Meta Muse Code and Devin accounts, with Devin connected through the --devin-login option.
- CLIProxyAPI includes a reusable Go SDK for embedding the proxy in other programs.
How it works
CLIProxyAPI runs as a local proxy server. You authenticate CLI accounts through simple login flows or add API keys, then point an OpenAI, Gemini or Claude-compatible client at the proxy. It forwards requests to the connected providers and spreads load across accounts. A Management API is available, and release builds for Linux and FreeBSD are published.
How to install and start using CLIProxyAPI
Requirements
- Accounts or API keys for the providers you want to route, such as Codex, Claude Code, Gemini or Grok.
- The default Linux build needs GLIBC 2.17 or later; a no-plugin build exists for musl-based or older systems like OpenWrt.
First steps
- Read the CLIProxyAPI guides at help.router-for.me to set up the proxy.
- Log in to provider accounts such as Codex, Claude Code, Grok Build or Gemini through the CLI authentication flows.
- Point any OpenAI, Gemini or Claude-compatible client or SDK at the CLIProxyAPI endpoint.
- On desktop, optionally use the EasyCLIProxyAPI client for graphical configuration and one-click start and stop.
Who CLIProxyAPI is for
- Developers who want to use CLI subscription accounts from standard OpenAI, Gemini or Claude-compatible clients.
- Teams spreading requests across several accounts of the same provider.
- Go developers who want to embed a multi-provider proxy through the SDK.
- Users running Claude Code against a Codex backend.
Limitations to know
- CLIProxyAPI no longer ships built-in usage statistics since v6.10.0; separate tools like CPA Usage Keeper are needed.
- CLIProxyAPI no-plugin builds for musl Linux and FreeBSD arm64 do not support dynamic library plugins.
- CLIProxyAPI model availability for Gemini varies by channel, such as Gemini API, AI Studio, Vertex AI, Gemini CLI or Antigravity.
- Antigravity lists its Claude thinking models only for Google AI Pro (non-trial), Google AI Ultra and Enterprise plans.
Is CLIProxyAPI growing? Usage data
In the week of Oct 25–31, 2026, CLIProxyAPI ranked #33 on the Devtoolwatch Board and #6 in Inference and training, with a momentum score of 81 out of 100.
Show the weekly numbers
| Week of | New stars |
|---|---|
| Aug 9, 2026 | 833 |
| Aug 16, 2026 | 1k |
| Aug 23, 2026 | 925 |
| Aug 30, 2026 | 1.4k |
| Sep 6, 2026 | 1k |
| Sep 13, 2026 | 1k |
| Sep 20, 2026 | 791 |
| Sep 27, 2026 | 845 |
| Oct 4, 2026 | 779 |
| Oct 11, 2026 | 846 |
| Oct 18, 2026 | 683 |
| Oct 25, 2026 | 1k |
The Board ranks tools by four signals each week: new stars, new stars for the repo's size, added downloads and download growth beyond the market. How the ranking works.
CLIProxyAPI alternatives
Other LLM inference and training tools on the Board in the week of Oct 25–31, 2026, by momentum:
| Rank | Tool | Stars | Downloads/wk |
|---|---|---|---|
| #1 | dsh-our-free-modeldsh-our-free-model is a dsh plugin that provides DeepSeek V4.1 Flash, Kimi K3 and other models without login, sign-up or API key. | 54.3k | – |
| #2 | magpiemagpie is a local gateway and app that lets coding agents like Claude Code, Codex and Gemini CLI use any provider's model. | 26.9k | – |
| #3 | StrataStrata is a local inference engine and app that runs large open models like Qwen3.8-Flash-Next on consumer hardware with… | 37.1k | – |
| #4 | edge0edge0 is an open-source streaming inference framework that runs large sparse mixture-of-experts models on consumer hardware by streaming… | 8.9k | – |
| #5 | OmniRouteOmniRoute is an open-source AI gateway that routes requests across many model providers through one OpenAI-compatible endpoint, with… | 83.2k | 106k |
| #7 | codex-chatgpt-webcodex-chatgpt-web is a launcher that lets Codex use the ChatGPT Web models on your account, including Pro, through browser automation. | 15.3k | – |
Recent CLIProxyAPI releases
CLIProxyAPI FAQ
Is CLIProxyAPI free and open source?
Yes. CLIProxyAPI's source code is on GitHub (router-for-me/CLIProxyAPI) under the MIT license, so you can use it for free.
Is CLIProxyAPI still maintained?
Yes. The router-for-me/CLIProxyAPI repository was last updated on Nov 1, 2026, and the latest release, v8.0.51 on GitHub, came out on Nov 1, 2026.
How popular is CLIProxyAPI?
CLIProxyAPI has 57.1k GitHub stars as of Nov 1, 2026. It gained 1k new stars in the week of Oct 25–31, 2026, against a 12-week average of 933 a week. That made it #6 among LLM inference and training tools on the Devtoolwatch Board.
CLIProxyAPI vs LiteLLM: how do they compare?
CLIProxyAPI and LiteLLM are both tracked by Devtoolwatch. CLIProxyAPI has 57.1k GitHub stars and LiteLLM has 62.5k. LiteLLM is an open source AI gateway and Python SDK that calls 100+ LLM providers through one OpenAI-format interface. LiteLLM review.
CLIProxyAPI vs Sub2API: how do they compare?
CLIProxyAPI and Sub2API are both tracked by Devtoolwatch as LLM inference and training tools. CLIProxyAPI has 57.1k GitHub stars and Sub2API has 45.2k. Sub2API review.
What are the best alternatives to CLIProxyAPI?
Other LLM inference and training tools on the Devtoolwatch Board in the week of Oct 25–31, 2026, by momentum: dsh-our-free-model (#1), magpie (#2), Strata (#3), edge0 (#4), OmniRoute (#5). The alternatives table above has their numbers.
Which clients can connect to CLIProxyAPI?
CLIProxyAPI works with any OpenAI-compatible client or SDK, including the Responses API, as well as Gemini-compatible clients, including Interactions, and Claude-compatible clients.
Does CLIProxyAPI support multiple accounts?
Yes. CLIProxyAPI supports multiple accounts with round-robin load balancing for Gemini, OpenAI, Claude and Grok. It also balances across multiple AI Studio Build, Claude Code, Codex and Grok Build accounts.
Does CLIProxyAPI have a graphical interface?
CLIProxyAPI itself is a server. The EasyCLIProxyAPI desktop client adds a graphical configuration UI, automatic updates, system tray integration and one-click start and stop. Community consoles such as CPA-Manager-Plus and Oh-My-CPA add management dashboards.
How do I track usage with CLIProxyAPI?
CLIProxyAPI has had no built-in usage statistics since v6.10.0. The README points to CPA Usage Keeper, CPA-Manager-Plus or Oh-My-CPA. These tools store request data in SQLite and show dashboards.
Can I add other upstream providers to CLIProxyAPI?
Yes. CLIProxyAPI can use OpenAI-compatible upstream providers such as OpenRouter through its config. The Go SDK also includes a custom provider example in examples/custom-provider.
Sources
CLIProxyAPI README badge
Maintainers can show the tool's weekly Board rank in their README:
[](https://index.devtoolwatch.com/tools/router-for-me-cliproxyapi/)How this page is made: Devtoolwatch writes each review from the project's README, releases, package metadata and website, with an AI model, then checks every claim against the source it cites and drops what the sources don't support. The numbers come from Devtoolwatch's daily GitHub snapshots, GitHub's stargazer history, and the npm and PyPI download APIs. Spotted an error? Email [email protected].