Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/kitephp/CLIProxyAPI-Tray/llms.txt

Use this file to discover all available pages before exploring further.

CLIProxyAPI Tray manages CLIProxyAPI versions independently of any system-level package manager. Each version is downloaded from GitHub Releases and stored in its own subfolder, so multiple versions can coexist on disk without conflict.

​
How versions are stored

Every downloaded release lives under the versions/ directory inside your install folder: 
versions/
├─ v6.7.35/
│  └─ cli-proxy-api.exe
└─ v6.7.37/
   └─ cli-proxy-api.exe
The active version is recorded in settings.json as the version field (e.g. "v6.7.37"). When you start CLIProxyAPI, the tray looks up that tag and launches versions/{tag}/cli-proxy-api.exe.

​
Download package naming

The tray constructs the asset filename from the version tag and detected architecture: 
CLIProxyAPI_{version}_windows_{arch}.zip
Examples:
  • CLIProxyAPI_6.7.37_windows_amd64.zip
  • CLIProxyAPI_6.7.37_windows_arm64.zip
The zip is fetched from the router-for-me/CLIProxyAPI GitHub Releases page. After extraction, cli-proxy-api.exe is copied to versions/{tag}/ and the zip is deleted.

​
Architecture detection

The tray detects your CPU architecture at runtime and stores it in settings.json as arch:
ValueMeaning
amd64Standard 64-bit x86 Windows (most desktops and laptops)
arm64Windows on ARM (Surface Pro X, Snapdragon-based devices)

​
First-time install

If no version is installed when you click Start:
1

Tray fetches the latest tag

The tray queries the GitHub API for the latest release of router-for-me/CLIProxyAPI.
2

Download confirmation dialog

A dialog shows the latest version and your architecture. Click Yes to download.
3

Download and extract

The zip is downloaded to a temp directory, extracted, and cli-proxy-api.exe is copied to versions/{tag}/.
4

State saved

The new version tag and arch are written to settings.json. The temp directory is deleted.
If you click No at the download prompt, the tray scans the versions/ directory for any existing binary and uses the newest one found. If none exist, the tray cannot start CLIProxyAPI.

​
Updating versions

See Auto update and manual update for the full update flow. Key points:
  • Old versions are never deleted automatically — they accumulate in versions/
  • If a download fails, the temp directory is cleaned up and state rolls back to the previous version
  • You can manually delete old version folders from versions/ to reclaim disk space
If you delete the versions/ directory entirely, the tray will prompt you to download again the next time you click Start.

Build docs developers (and LLMs) love

Get started for freeTalk to us