EasyCLIProxyAPI

Overview

EasyCLIProxyAPI is a graphical desktop management tool built on CLIProxyAPI. It brings core 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 application is built with Tauri, React, and Rust. It can carry a matching CLIProxyAPI core archive, making first-time setup and offline installation easier.

Feature Tour

Home dashboard and local API endpoints

The Home page provides a quick overview of the local proxy runtime and ready-to-use API endpoints:

• Start, stop, restart, and refresh the CLIProxyAPI core.
• View installation state, runtime state, process ID, and listening port.
• Copy ready-to-use OpenAI, Claude, and Gemini-compatible API endpoints.
• Check local connectivity and the application/core version at a glance.

Core installation, version comparison, and offline installation are available from the Version Management page. You can switch between 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.

Application and core updates are each checked once in the background at startup and automatically whenever you enter Version Management. Their respective Check for Updates buttons remain available for manual checks. Re-rendering the page does not trigger another check. Changing download sources does not trigger a check, and reopening the page preserves the saved source. Checks do not automatically download or install updates.

OAuth account authorization

The OAuth page centralizes browser-based authorization for supported providers:

• Codex OAuth
• Claude OAuth
• Antigravity OAuth
• Kimi OAuth
• xAI OAuth

EasyCLIProxyAPI opens the authorization page in the browser and supports completing the callback flow when an automatic redirect is unavailable.

API provider aggregation

The provider workspace manages upstream API credentials and endpoints by protocol or provider:

• Codex
• OpenAI-compatible providers
• DeepSeek
• Claude
• 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.

Plugins

The Plugins page manages installed core plugins, their enabled state and typed configuration. Browse the plugin store to install, update or select a release version, configure additional stores and environment-based authentication, open pages and sign in to accounts provided by enabled plugins. Pages provided by enabled plugins appear as a submenu under Plugins in the sidebar (below Versions), expanded when space allows and collapsible otherwise. A plugin page opens in a native webview that fills the content area, with small Back, Reload and Open in browser buttons in its bottom-right corner (drag the grip to move them; double-click it to reset); new-window links open in the system browser. 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. Refreshing Local plugins checks installed plugins for updates and shows an update action on their cards. Public GitHub releases are checked directly using the configured GitHub token or the app's GITHUB_TOKEN environment variable; auth-required entries keep the core's authentication flow. Refreshing the Plugin store only reloads the plugin list. Installation queries the latest release unless a version is selected.

Usage history and token analytics

The Usage page helps you understand local request activity and token consumption:

• Review request totals, token counts, success rate, throughput, cache hit rate, and estimated cost.
• Filter usage by time, model, provider, source, key, and result.
• Inspect request/token trends and input, output, reasoning, and cache usage.
• Browse request details, analysis views, and price statistics.
• Collect through CPA's real-time usage subscription with a durable local inbox and automatic HTTP fallback.
• Upgrade legacy usage databases once at startup after saving a backup under usage-records/backups.

Agent client configuration

The Agents page detects installed desktop and CLI clients and helps connect them to the local proxy. Supported clients include:

• Claude Code
• Claude Desktop
• Codex
• OpenCode
• OpenClaw
• Hermes Agent
• Pi (with the CLIProxyAPI provider extension)
• ZCode
• WorkBuddy / WorkBuddy AI
• Antigravity CLI
• Kimi Code
• Grok Build
• Oh My Pi

For supported clients, the application can synchronize the available model catalog, select a default model, back up the original configuration before applying managed settings, and restore the previous configuration.

In Agents → Management → Configuration directory, enter or browse to the directory containing the client's configuration files, such as .claude or .codex (not the home directory). Windows also accepts WSL UNC paths such as \\wsl$\Ubuntu\home\user\.claude and \\wsl.localhost\Ubuntu\home\user\.codex. Each client remembers its own directory; clearing it restores the default. This setting changes configuration access, not how executables are launched.

Antigravity CLI connects through CPA's Gemini-compatible API. Launch the CLI from CPA to supply its endpoint and API key for that process. Running agy directly requires setting those environment variables yourself.

This is the beginning of the README. Read the rest at the original. Read the full README ↗