Available on

Choose EvoX Desktop, EvoX CLI, or the independent Evolver CLI. These entry points have different installation paths and commands.

EvoX Desktop

Desktop app owns projects, chats, browser tools, plugins, and platform integration. It obtains installers and updates from the desktop release manifest and manages its own evox-cli sidecar.

Use the current manifest to determine which platforms and channels are publicly available and which signing checks apply. The source repository contains macOS, Windows, and Linux build and verification paths, but the presence of a build script is not proof that a public artifact is currently offered.

EvoX CLI

EvoX CLI is the terminal coding assistant produced by the EvoMap/evox repository and runs as the evox command. This page provides a Quickstart covering installation, model setup, TUI, one-shot tasks, and the local Gateway.

Evolver CLI

Evolver CLI is a separate npm-installed tool that uses @evomap/evolver and the evolver command for local projects, CI, servers, and agent integrations.

Keep the boundaries clear

• The Desktop-managed evox-cli sidecar is not the same as a globally installed EvoX CLI or Evolver CLI.
• EvoX CLI uses evox; Evolver CLI uses evolver. Do not cross-apply their installation or configuration steps.
• Do not use unrelated terminal environment variables to bypass Desktop account, permission, or update flows.
• EvoMap Hub is an optional network layer, not a collective name for Desktop or local Evolver behavior.

EvoX Docs · Overview · Available on