EvoX overview
EvoX Desktop is the desktop application for projects, chats, files, browser work, plugins, and local runtime workflows. It is maintained in EvoMap/evox-desktop, built with Wails, Go, and React, and supervises an embedded evox-cli sidecar.
Evolver is a separate deliverable. Install @evomap/evolver to use its CLI, Proxy, MCP, and GEP experience workflows in a project or agent runtime. EvoMap Hub provides the network layer for nodes, assets, and tasks.
Choose an entry point
| Goal | Entry point | Notes |
|---|---|---|
| Create projects, chats, and ongoing work on the desktop | EvoX Desktop | Use the current official download manifest; platform and channel availability come from that manifest. |
| Run Evolver in a Git repository or agent workflow | Evolver CLI | Install with npm and run evolver from a terminal. |
| Add experience search and reuse to an MCP-compatible agent | Evolver Proxy / MCP | Search and express a Recipe first, then fall back to Genes or Capsules when needed. |
| Join network asset, Worker, or Validator workflows | EvoMap Hub | Requires a separate node identity, network authorization, and the relevant controls. |
EvoX Desktop and Evolver CLI are not graphical and command-line editions of one product. Desktop manages its embedded runtime; standalone Evolver CLI is intended for development and automation workflows.
What this documentation covers
- Get started: install the app, complete a first task, or import existing experience.
- Features: projects, chats, browser tools, plugins, scheduled work, visualizations, and other desktop capabilities.
- Configuration: keep Desktop settings separate from standalone Evolver configuration.
- Developers: Evolver CLI, GEP, MCP, A2A, and repository boundaries.
- Security: protect local identity, assets, execution, releases, and data.
- Administration: operate nodes, assets, network tasks, releases, and recovery.
Start here
- Desktop users should begin with Get EvoX and Use EvoX.
- Developers should begin with Install Evolver CLI.
- Configure Hub, Worker, Validator, publishing, or ATP only when the workflow needs network participation.
This documentation follows the current product source, package metadata, and verified commands. When UI, defaults, or commands change, verify the installed version before updating the guidance.
EvoX Docs · Overview