Model or dataset
router-for-me/EasyCLIProxyAPI avatar
router-for-me/EasyCLIProxyAPI

EasyCLIProxyAPI: A Tauri Desktop Console for CLIProxyAPI, With Agent Config Rewriting and a Fast Release Cadence

A desktop GUI for CLIProxyAPI and a tool for automatically configuring popular AI agents.

3,629 stars332 forksRustMIT

At a glance

What is it?
EasyCLIProxyAPI wraps the CLIProxyAPI core in a Tauri, React and Rust desktop app that handles OAuth logins, provider aggregation, usage records and agent client configuration. It edits real configuration files, so the backup and directory rules matter.
Who is it for?
EasyCLIProxyAPI suits people who already run CLIProxyAPI or want one local OpenAI, Claude and Gemini compatible endpoint with a graphical console and automatic agent configuration. It is a poor fit if you want a stable, slow-moving tool or a read-only helper: it rewrites client config files, edits Codex session history in an experimental mode, and ships a new version almost daily.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Rust, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • router-for-me/EasyCLIProxyAPI3,629 ★ · +1,552
Star history
Repository2026-09-112026-11-15
router-for-me/EasyCLIProxyAPI2.1k3.6k

1,552 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The app manages the CLIProxyAPI core and does not replace it

EasyCLIProxyAPI is described as a graphical desktop management tool built on CLIProxyAPI. It brings lifecycle management, OAuth authorization, API provider aggregation, protocol conversion, credential management, quota inspection, usage records, model aliases and agent client configuration into one interface. The proxy itself is the separate CLIProxyAPI core.

The application is built with Tauri, React and Rust, and the repository includes a core-version.txt file plus build and run scripts for both shell and PowerShell. The app can carry a matching CLIProxyAPI core archive, which makes first-time setup and offline installation easier. The package manifest declares bun as its package manager and pairs `tsc` with `vite build` for the front end.

The Home page shows the proxy runtime: you can start, stop, restart and refresh the core, view installation state, runtime state, process ID and listening port, and copy ready-to-use OpenAI, Claude and Gemini compatible endpoints. The consequence of this split is two moving parts. A GUI release and a core release have separate versions, and the app displays both so you can see when they drift apart.

Core and app updates are checked quietly, never installed without you

Core installation, version comparison and offline installation live on the Version Management page. You can pick among the official GitHub, GitCode and GitHub mirror proxies, or add custom HTTPS mirror prefixes. Application and core updates prefer the selected channel and fall back automatically.

Update checks are deliberately restrained. The app and the core are each checked once in the background at startup and again whenever you enter Version Management. Each has a Check for Updates button for manual checks. Re-rendering the page does not trigger another check, and changing download sources does not trigger one either. Reopening the page preserves the saved source.

Most importantly, checks do not automatically download or install updates. That protects a long-running proxy from changing underneath you, but it also means nothing will upgrade for you. With releases arriving almost every day, an unattended install can fall many versions behind, and you have to go to the page and apply the update yourself.

OAuth login covers five providers and has a manual callback for blocked redirects

The OAuth page centralises browser-based authorisation for Codex, Claude, Antigravity, Kimi and xAI. The app opens the authorisation page in your browser and supports completing the callback flow when an automatic redirect is unavailable.

That fallback matters in practice. Redirects to a local address can fail when a browser, firewall or remote desktop setup interferes, and the manual path lets you finish the login anyway.

The tagline on the project is to make tokens free, as in freedom, which describes the aim of reusing your own accounts through one local endpoint. What the README does not say is anything about each provider's terms for this kind of use. The tool signs into accounts you hold, and whether a given plan allows routing its access through a local proxy is a question for that provider's terms, not for this app. Check them before connecting a subscription account you depend on.

One local endpoint speaks OpenAI, Claude and Gemini formats

The provider workspace manages upstream credentials and endpoints by protocol or provider: Codex, OpenAI-compatible providers, DeepSeek, Claude and Gemini. You can add multiple connections, search existing entries, refresh provider state, and use them through the unified local CLIProxyAPI endpoint.

Requests and responses can be converted between supported OpenAI, Claude, Gemini and compatible formats. That conversion is what lets a client written for one API talk to a provider that speaks another. The README gives no list of which request fields survive conversion, so features specific to one provider, such as a particular reasoning option, are not guaranteed to cross over.

Model aliases add another layer. You can create client-visible model names and map them to provider models and reasoning levels, so a client sees a stable name while you change what stands behind it. For people asking what CLIProxyAPI is used for, this is the answer in the README: it is a local proxy that aggregates providers and converts protocols, and EasyCLIProxyAPI is its desktop console.

Agent setup rewrites client config files, with backup and a precise directory rule

The Agents page detects installed desktop and CLI clients and connects them to the local proxy. The list is Claude Code, Claude Desktop, Codex, OpenCode, OpenClaw, Hermes Agent, Pi with the CLIProxyAPI provider extension, ZCode, WorkBuddy, Antigravity CLI, Kimi Code, Grok Build and Oh My Pi. For supported clients the app can synchronise the model catalogue, select a default model, back up the original configuration before applying managed settings, and restore the previous configuration.

The directory field is easy to get wrong. Under Agents, Management, Configuration directory, enter the directory containing the client's configuration files, such as `.claude` or `.codex`, and not the home directory. Windows also accepts WSL UNC paths such as `\\wsl$\Ubuntu\home\user\.claude`. Each client remembers its own directory, and clearing it restores the default. The setting changes configuration access, not how executables are launched.

Antigravity CLI needs special handling. It connects through CPA's Gemini-compatible API, so launch the CLI from CPA to supply its endpoint and API key for that process. Running `agy` directly means setting those environment variables yourself.

Editing Codex session context is experimental and changes real history

Codex Session Management includes an Edit Context feature marked Experimental. The README spells out how it behaves. It reads messages only after you select a session. Listing and pagination query SQLite, the session index and directory metadata without opening or prefetching rollouts. Unindexed sessions are found by their standard rollout filenames, and missing workspace and provider details load when the editor opens.

The warnings are direct: close the target session before saving, because saves modify real local history and create backups. Manually renamed files that have no session ID in their filename or a database path are not discovered by scanning their contents, so a renamed rollout may never appear in the list.

The lesson is to treat this as a power tool. Edit one session you can afford to damage first, confirm the backup exists, and only then touch history you care about. The usage side has a similar one-time risk: legacy usage databases are upgraded once at startup, after a backup is saved under `usage-records/backups`, so keep that folder until you are sure the upgrade went well.

Usage analytics and plugins add power, and the release cadence is almost daily

The Usage page shows request totals, token counts, success rate, throughput, cache hit rate and estimated cost. You can filter by time, model, provider, source, key and result, inspect input, output, reasoning and cache usage, and browse request details and price statistics. Collection uses CPA's real-time usage subscription with a durable local inbox and automatic HTTP fallback. The cost figure is an estimate, so do not treat it as a bill.

The Plugins page manages installed core plugins, enabled state and typed configuration, with a plugin store for installing, updating or selecting a release version. Third-party installations require source review and a typed confirmation. The page detects unsupported core builds and shows a restart action when an installation or removal requires it. Public GitHub releases are checked with the configured GitHub token or the app's `GITHUB_TOKEN` environment variable.

The release list shows v0.3.68 on 2026-11-03, a preview-only build on 2026-11-01 and v0.3.67 on 2026-11-02, and the last push was on 2026-11-02. A 0.3.x version moving this fast means features and behaviour change often, so read the notes before each upgrade.

Editorial conclusion

EasyCLIProxyAPI suits people who already run CLIProxyAPI or want one local OpenAI, Claude and Gemini compatible endpoint with a graphical console and automatic agent configuration. It is a poor fit if you want a stable, slow-moving tool or a read-only helper: it rewrites client config files, edits Codex session history in an experimental mode, and ships a new version almost daily.

Frequently asked questions

What is CLIProxyAPI used for?

CLIProxyAPI is the local proxy core that EasyCLIProxyAPI manages. It aggregates API providers behind one local endpoint and converts requests between OpenAI, Claude, Gemini and compatible formats.

Can CLIProxyAPI be used to access Claude Code?

EasyCLIProxyAPI lists Claude Code among the clients it can configure, and offers Claude OAuth and a Claude provider. It can back up and restore the client's original configuration.

What is EasyCLIProxyAPI built with?

EasyCLIProxyAPI is built with Tauri, React and Rust. It is licensed under MIT and can carry a matching CLIProxyAPI core archive for offline installation.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. router-for-me/EasyCLIProxyAPI on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/router-for-me-easycliproxyapi.svg)](https://hysenlabs.com/projects/router-for-me-easycliproxyapi)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/router-for-me-easycliproxyapi.svg)](https://hysenlabs.com/projects/router-for-me-easycliproxyapi)

Was this useful?