一覧へ戻る
A desktop GUI for CLIProxyAPI and a tool for automatically configuring popular AI agents.
- star 数
- 3,321
- watcher 数
- 8
- fork 数
- 299
- issue 数
- 95
- 最終更新
- 2026/10/31
gem-hunterA desktop GUI for CLIProxyAPI and a tool for automatically configuring popular AI agents.
A portable desktop console for CLIProxyAPI.
Our goal is to make tokens free—as in freedom.
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.
The Home page provides a quick overview of the local proxy runtime and ready-to-use API endpoints:
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.
The OAuth page centralizes browser-based authorization for supported providers:
EasyCLIProxyAPI opens the authorization page in the browser and supports completing the callback flow when an automatic redirect is unavailable.
The provider workspace manages upstream API credentials and endpoints by protocol or provider:
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.
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.
The Usage page helps you understand local request activity and token consumption:
usage-records/backups.
The Agents page detects installed desktop and CLI clients and helps connect them to the local proxy. Supported clients include:
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.
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.
Codex Session Management → Edit Context (Experimental) reads messages only after a session is selected. Listing and pagination query SQLite, the session index and directory metadata without opening or prefetching rollouts. Unindexed sessions are discovered by their standard rollout filenames; missing workspace and provider details load when the editor opens. Metadata is collapsed by default, with message-role filters retained. Close the target session before saving; saves modify real local history and create backups. Manually renamed files without a session ID in their filename or a database path are not discovered by scanning their contents.
Every Windows release publishes both the complete ZIP and the legacy update ZIP. This keeps in-app updates available to older clients that have not migrated yet, while newer clients use the complete package so the bundled core can be updated too.
Current Windows, Linux, and macOS release packages support in-app automatic updates. Linux replaces the portable application files while preserving runtime data, and macOS replaces the signed application bundle. Each platform waits for the new version to confirm a successful launch and rolls back automatically if startup fails. The installation directory must be writable by the current user.
Existing Linux and macOS installations need one manual upgrade to a release that includes the cross-platform auto-update marker. In-app updates are available after that release has been launched once.
If you are running v0.2.5 or earlier, perform one manual migration: exit EasyCLIProxyAPI, download the latest complete Windows ZIP for your architecture, then copy the contents of its top-level directory over the existing installation directory. Do not delete the existing directory first; user data such as config.toml, oauth, and cpa-core/config.yaml will remain in place. After launching the new version, later releases can use in-app automatic updates.
GitHub Actions builds the following release packages:
| Operating System | Architecture | Package |
|---|---|---|
| Windows | amd64, aarch64 | ZIP |
| macOS | amd64, aarch64 | DMG |
| Linux | amd64, aarch64 | TAR.GZ |