Install and update the CLI

The published CLI package includes platform packages for macOS arm64 and Intel, Linux arm64 and x64, and Windows x64. Windows arm64 and musl packages are not currently listed. The npm distribution needs a package-manager runtime; a standalone binary can run without one when a public standalone release is available.

Check your operating system and CPU architecture before installing. If a matching platform package is absent, stop at the compatibility check instead of substituting another architecture's binary. For a workstation managed by your organization, use its approved package source and verify that it serves the same published version.

Install and verify

Follow the installation quickstart to check the registry version, install the package and use the commands supported by that version. Then verify the installed executable:

unlimgpt --version
unlimgpt --help

The first command prints the installed version; root help lists available commands. Compare unlimgpt --version with npm view @unlimgpt/cli version and find the command in root help. Published version 0.1.2 does not support subcommand --help. If configure or keys is absent, use the browser key flow and the first HTTP request, or update when a newer version appears.

For an update, run unlimgpt update. It prints the published version and the exact npm install -g @unlimgpt/cli@<version> command. unlimgpt update --yes runs that command and does not change profiles, sign-in or API keys. Repeat the version and root help checks afterward. Replacing the executable does not rotate a key, and removing the package does not revoke a grant. Before removing the package, decide whether to log out and revoke its dedicated keys. If the executable has already been removed, perform those actions in Settings and API keys from a trusted browser.

Next: configure a client.