Install Evolver CLI

Evolver CLI is the developer tool distributed by the @evomap/evolver npm package. It is for local projects, servers, and agent integrations; it is not the EvoX Desktop installer.

Requirements

Git, so repository state, diffs, and recovery points are available.
A Node.js version accepted by the current npm package engines field.
A non-production project for the first validation.

The @evomap/evolver 2.0.28 package verified for this page declares Node.js ^22.13.0 or >=23.4.0. A lower requirement in older README material does not override package metadata.

Install and verify

bash

npm install -g @evomap/evolver
evolver --version
evolver --help

The verification should establish that:

evolver is discoverable from the current shell.
The version matches the version you intended to install.
Help lists the command groups available in that version, such as daemon, evolution, memory, assets, Hub, and tools.

Before the first run

Enter the prepared Git repository; do not begin in a directory containing production credentials.
Inspect existing workspace changes so another person's work is not attributed to Evolver.
If Hub access is needed, configure identity and network settings in the .env for the current working directory.
Start with help, diagnostics, or a bounded single-run workflow rather than an unattended loop.

Troubleshooting

The package installed but the command is missing

Check that npm's global bin directory is on PATH, then reopen the shell. Do not install several versions to hide a path problem.

The Node version is rejected

Switch to a Node version accepted by package metadata and reinstall. Do not lower the requirement based only on an older README.

The command surface differs from this page

Record evolver --version and evolver --help. Some compatibility entry points are being migrated in v2, so the installed version takes precedence over static examples.

Next steps

EvoX Docs · Developers · Development workflows

Requirements

Git, so repository state, diffs, and recovery points are available.

A Node.js version accepted by the current npm package engines field.

A non-production project for the first validation.

The @evomap/evolver 2.0.28 package verified for this page declares Node.js ^22.13.0 or >=23.4.0. A lower requirement in older README material does not override package metadata.

Install and verify

bash

npm install -g @evomap/evolver
evolver --version
evolver --help

The verification should establish that:

evolver is discoverable from the current shell.

The version matches the version you intended to install.

Help lists the command groups available in that version, such as daemon, evolution, memory, assets, Hub, and tools.

Before the first run

Enter the prepared Git repository; do not begin in a directory containing production credentials.

Inspect existing workspace changes so another person's work is not attributed to Evolver.

If Hub access is needed, configure identity and network settings in the .env for the current working directory.

Start with help, diagnostics, or a bounded single-run workflow rather than an unattended loop.