Beta
Discord Download

CLIProxyAPI vs AutoRouter

If you’re looking at CLIProxyAPI to use your Claude and ChatGPT plans in Codex and Claude Code, AutoRouter does that with nothing to host. It’s a Mac menu-bar app that pools the plans you already pay for, picks the model for each turn and needs no keys. CLIProxyAPI is a free, open-source proxy you set up yourself: you bring the accounts or API keys and write the config. This page covers how CLIProxyAPI works, then how the two compare.

AutoRouter A Mac app that picks a model for each turn. $0/mo on your plans Download CLIProxyAPI An open-source API proxy you run yourself. $0open source
Price $0 on your plans, Pro $50 a month Free, MIT licensed
Fee on tokens Provider’s price plus 10% on paid models None, you pay your providers
Runs on Your Mac, macOS 14 or later macOS, Linux, Windows, FreeBSD or Docker
Tools Codex, Claude Code, Cursor, Claude Desktop, T3 and Terminal Any OpenAI, Gemini or Claude compatible client, with guides for Claude Code, Codex and four more
Setup Install, sign in, click Enable Install, write config.yaml, log in accounts, point each client at it
Your plans Claude, ChatGPT, Grok and Gemini plans, in any harness Codex, Claude Code, Grok Build, Gemini and other account logins
Model choice Your rules, then a model that clears the quality bar The model each client asks for, through your aliases
Each request Every turn shows its model, cost and why Usage statistics through separate community tools
Requests go Through AutoRouter’s servers to each provider Through the proxy you run, to each provider
  • A model picked for each turn, with no config to write
  • Models included, with no keys or proxy to run
  • Your plans stacked and used first
  • Rollout to every Mac in a team through MDM

Sources checked November 17, 2026: CLIProxyAPI README (version 8.0.76), quick start, configuration docs, Claude Code guide, Codex guide, Web UI docs, model router plugin docs and AutoRouter pricing. AutoRouter wrote this page. See every comparison.

How CLIProxyAPI works

What the project is, how setup works, and how it spreads requests across your accounts.

One API in front of your accounts

CLIProxyAPI is an open-source project by router-for-me on GitHub, MIT licensed and written in Go, with more than 58,000 stars. Its README calls it a proxy server that gives OpenAI, Gemini, Claude, Codex and Grok compatible API interfaces, so any OpenAI (including Responses), Gemini or Claude compatible client or SDK can reach the accounts you connect (README).

You connect Codex, Claude Code and Grok Build accounts through OAuth logins, Gemini through API, AI Studio, Vertex AI, Gemini CLI or Antigravity accounts, and Kimi, Muse Code and Devin accounts. API keys and OpenAI-compatible upstreams such as OpenRouter go in the config. A Go SDK lets you embed the proxy in your own program.

How setup works

Install it with brew install cliproxyapi on a Mac, an installer script or the AUR on Linux, a release download on Windows, or the Docker image (quick start). Then write config.yaml. The docs’ example looks like this:

port: 8317
auth-dir: "~/.cli-proxy-api"
api-keys:
  - "your-api-key-1"
routing:
  strategy: "round-robin"

Log in each account, for example with ./cli-proxy-api --claude-login, which opens a browser. Then point each client at the proxy: Claude Code gets ANTHROPIC_BASE_URL set to http://127.0.0.1:8317 and one of your API keys in settings.json, and Codex gets a model provider in config.toml with that address plus /v1 (Claude Code guide, Codex guide).

Load balancing, failover and aliases

With several accounts for one provider, requests rotate round-robin by default, or fill one account first. When the account a session is bound to becomes unavailable, it fails over automatically, and failed requests retry on errors such as 403, 500 or 503. Aliases rename model IDs for listing and routing, so a client can ask for a name you chose (configuration docs). A model router plugin can decide where a request runs, with logic its author writes.

Web UI and desktop clients

The proxy serves a web management center at /management.html, backed by a Management API. For desktop use, the README recommends the EasyCLIProxyAPI client, with a graphical config screen, automatic updates, a tray icon and one-click start and stop. The README also lists community apps built on CLIProxyAPI, including Mac menu bar apps and Windows tray apps.

What it does well

  • It’s free and open source, so you can read the code that handles your requests.
  • It runs on macOS, Linux, Windows and FreeBSD, in Docker, or on a server you host.
  • Any client that speaks the OpenAI, Gemini or Claude API can use it, including your own scripts and SDKs.
  • It pools many accounts per provider, with round-robin or fill-first balancing and automatic failover.
  • Plugins can add providers, translate requests and route models, and the Go SDK embeds it in other programs.
  • A large ecosystem of community dashboards, tray apps and ports builds on it.

Where it gets harder

  • You choose the model. CLIProxyAPI serves the model each client asks for, through aliases you write, and doesn’t judge how hard a request is.
  • You install it, write the YAML, log in each account and keep the proxy running while you work.
  • Each client needs its own settings pointed at the proxy, with an API key you create for it.
  • Since version 6.10.0 it ships no built-in usage statistics, so spend and per-request views come from separate community tools.
  • The docs note that aliases don’t apply to API-key and OpenAI-compatible providers.

How AutoRouter differs

CLIProxyAPI gives your clients an endpoint and serves the model they ask for. AutoRouter chooses the model for every turn, using models it includes and the plans you already pay for.

It picks the model for each turn

AutoRouter shows up as one more model in the picker you already use. While it’s selected, it works out how hard each turn is and only considers models that clear the quality bar for it. Hard work goes to the strongest model your plans cover, and quick work to the one that costs you least. Your own plain-English rules go first, such as “Prefer GPT-6.1 Sol for code reviews.” Every turn shows its model, what it cost and why.

Nothing to host or configure

There’s no server to run, YAML to write or key to create. You sign in, sign in to your plans and click Enable for each app. Enabling adds AutoRouter to Codex’s config.toml and Claude Code’s settings.json after saving a copy of each file, and disabling it switches the app back. Frontier and open-weight models come with AutoRouter, kept current by its team.

Your plans, stacked in any harness

You can connect Claude, ChatGPT, Grok and Gemini plans and use them in any harness, such as a ChatGPT plan in Claude Code. When one account reaches its limit, AutoRouter moves to the one with the most room left before it spends any credit. Free connects two subscriptions and Pro connects any number.

Built for teams to roll out

Enterprise rolls AutoRouter out to every Mac through Jamf or another MDM, with nothing for anyone to set up. Admins get allowed models, team budgets and zero data retention in one place, spend by team, project or ticket, and SSO, SCIM and an audit log.

What it costs and what it can’t do

Routing across your plans is free. Pro is $50 a month with $20 of included usage, and paid models bill at the provider’s price plus 10%. It runs only on macOS 14 or later, and it doesn’t give you a raw API endpoint for your own scripts and SDKs the way CLIProxyAPI does. It sometimes misjudges how hard a task is. Requests pass through AutoRouter’s servers on their way to each provider; see privacy for what is kept.

Which one to choose

Choose CLIProxyAPI if you work on Linux, Windows or a server, want one API endpoint for any OpenAI, Gemini or Claude compatible client, pool many accounts, or want to host and read every line yourself for free.

Choose AutoRouter if you’re on a Mac and want each turn in Codex and Claude Code sent to the right model, with your plans used first and nothing to host, configure or keep running. For other options, read Model routers for Claude Code and Codex, compared.

Setup, side by side

The steps each one’s own docs give, as of November 17, 2026.

CLIProxyAPI

  1. Install brew install cliproxyapi on a Mac, the installer script on Linux, a release on Windows, or Docker.
  2. Configure Write config.yaml with the port, the API keys your clients use and the auth folder.
  3. Log in accounts Run a login such as ./cli-proxy-api --claude-login for each account, or add API keys.
  4. Point your clients Set Claude Code’s ANTHROPIC_BASE_URL and Codex’s model provider to the proxy’s address.

AutoRouter

  1. Download AutoRouter for macOS, signed and notarized by Apple.
  2. Sign in Sign in or create a free account, then sign in to your plans.
  3. Enable your apps Allow Accessibility and click Enable for each app.
  4. Pick AutoRouter In a new session, choose AutoRouter from Codex’s model menu, or with /model in Claude Code.

Questions

What people ask about CLIProxyAPI.

What is CLIProxyAPI?

A free, open-source proxy server by router-for-me that gives OpenAI, Gemini, Claude, Codex and Grok compatible API endpoints in front of the accounts and keys you connect. You run it on your own machine, a server or Docker, and point your coding tools and SDKs at it.

Is CLIProxyAPI free?

Yes. It’s MIT licensed and free. You pay for the accounts and API keys you connect, at their own prices.

Which accounts and providers does CLIProxyAPI support?

Its README lists Codex, Claude Code and Grok Build logins, Gemini through API, AI Studio, Vertex AI, Gemini CLI and Antigravity accounts, and Kimi, Muse Code and Devin accounts, plus API keys and OpenAI-compatible upstreams such as OpenRouter. AutoRouter connects Claude, ChatGPT, Grok and Gemini plans.

Does CLIProxyAPI work with Claude Code and Codex?

Yes. Its docs set Claude Code’s ANTHROPIC_BASE_URL to the proxy in settings.json and add a model provider to Codex’s config.toml, and they have guides for Droid, OpenCode, Grok Build and Pi too. AutoRouter adds itself to Codex and Claude Code when you click Enable.

Does CLIProxyAPI pick a model for me?

No. It serves the model each client asks for, renamed by any aliases you set, and spreads requests across your accounts round-robin or fill-first. A plugin can add routing logic that you write. AutoRouter picks a model for each turn after your own rules.

Does CLIProxyAPI have a GUI?

The proxy serves a web management center at /management.html. Its README recommends the EasyCLIProxyAPI desktop client for a graphical config screen, tray icon and one-click start and stop, and lists community apps built on it.

How is AutoRouter different from CLIProxyAPI?

CLIProxyAPI is a proxy you host and configure, with accounts and keys you add, on any system. AutoRouter is a Mac app with models included and no keys, picks a model for each turn with its reasons and cost, uses your plans first, and rolls out to a team’s Macs through MDM.

How do I move over from CLIProxyAPI?

Install AutoRouter, sign in to your plans and click Enable for each app. Enabling adds AutoRouter to the app’s own settings after saving a copy of the file, and other settings stay as they are. Rewrite any aliases you relied on as plain-English rules, such as “Prefer GPT-6.1 Sol for code reviews.” Disabling an app in AutoRouter’s settings switches it back.

What does AutoRouter cost?

Routing across your ChatGPT and Claude plans is free. Pro is $50 a month with $20 of usage, and paid models bill at the provider’s price plus 10%. See pricing, or estimate a month with and without AutoRouter in the savings calculator.