CLIProxyAPI

CLIProxyAPI is a proxy server that exposes OpenAI-, Gemini-, Claude-, Codex-, and Grok-compatible application programming interface (API) endpoints for…

  • AI
  • Tools & Utilities
CLIProxyAPI is a proxy server that exposes OpenAI-, Gemini-, Claude-, Codex-, and Grok-compatible application programming interface (API) endpoints for supported command-line interface (CLI) and OAuth providers. It lets homelab users connect multiple CLI provider accounts to standard client applications or software development kits (SDKs) through one locally hosted endpoint. Keep it on a trusted local area network (LAN) or virtual private network (VPN) because provider availability and authentication depend on upstream services.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

80/100 Excellent

Maintained
100last commit 7 days ago
Popular
9558,553 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
304 GB minimum RAM
Security check
94no serious findings, 1 minor, CI, tests

Availability: platform listings confirmed today, links checked 3 days ago

GitHub stars
58,553
Open issues
870
Last commit
2026-11-14
Latest release
v8.0.71
License
MIT
Activity
steady

Checked 7 days ago - source: GitHub (router-for-me/CLIProxyAPI)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 100 MB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Get the installable command first Download the pre-built CLIProxyAPI binary, make it executable, and move it to /usr/local/bin with sudo (administrator mode). This makes the cliproxy command available from a normal terminal, so if you skip it you may see “command not found”. source
  • Add your API key and port first Before starting the server, create a minimal config with the listening port, such as 8317, and your Gemini API key under gemini-api-key. Without the API key the app cannot use Gemini, and if the port is wrong or blocked, other devices or clients cannot connect to it. source
  • Keep your auth folder safe The auth-dir setting, such as ~/.cli-proxy-api, is where CLIProxyAPI stores local authentication data. Keep this folder backed up and private, because deleting or sharing it can force you to re-authenticate or expose access to your accounts. source
  • First run Set a 12-72 byte WebUI password, apply it, open the WebUI, connect provider accounts, and copy the generated API key. The API uses port 8317 and the dashboard uses port 8318. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why do I get 'command not found' after installing CLIProxyAPI?

Move the pre-built binary to /usr/local/bin with sudo and make it executable so the cliproxy command is available; skipping this step can cause command not found.

What should I set in a minimal CLIProxyAPI config before starting the server?

Set the listening port, such as 8317, and add your Gemini API key under gemini-api-key; without the key, the app cannot use Gemini.

What should I back up to avoid re-authenticating CLIProxyAPI accounts?

Back up the auth-dir folder, such as ~/.cli-proxy-api, because it stores local authentication data; deleting or sharing it can force re-authentication or expose account access.

What authentication methods are supported for Kimi, OpenAI, Gemini, Muse, and Devin?

Kimi supports OAuth or compatible API interfaces, and OpenAI models can be accessed through Codex OAuth. Gemini supports Gemini API, AI Studio, Vertex AI, Gemini CLI, or Antigravity accounts, while Muse uses Meta login or API keys and Devin uses --devin-login.

Answers sourced from deepwiki.com, deepwiki.com, github.com

Community

Collected 49 days ago - public community threads