Installation and first run

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 package requires Node.js ^22.13.0 or >=23.4.0. Verify the installed runtime with node --version before installing.

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 through a protected process environment or the entry point's explicit environment-file option. Do not assume the working directory's .env loads automatically.
Start with help, diagnostics, or a bounded single-run workflow rather than an unattended loop.

Complete the first useful run

Enter the prepared project and run:

bash

git status --short --branch
evolver doctor
evolver cycle capabilities --json
evolver review

Step	Inspect	Decision
Workspace status	Path, branch, existing changes	Existing work identified and scope correct
doctor	Dependencies, configuration sources, identity, and connectivity	Resolve diagnostics required by the selected capability
capabilities	Collection, injection, execution, validation, recovery	Select by supported behavior rather than installed host names
review	Pending Gene candidates	Prepare material if empty; otherwise follow Review and validation

These commands establish an installation and environment baseline. They do not approve candidates, publish assets, or establish autonomous code execution. Continue by constructing and validating a first Gene or connecting experience tools to an agent.

Initial diagnostics do not require automatic purchases, task intake, or resident operation. For network use, establish Hub and identity sources first. Assess local diagnostics separately from network connectivity.

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. Verify both the shell runtime and the runtime used by the service manager.

A command is not found

Use evolver --help and the selected command group’s help to inspect entry points and required arguments. Confirm that the shell resolves the intended executable before changing configuration.

Next steps

EvoX Docs · Developers · Standalone Evolver

Installation and first run

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 package requires Node.js ^22.13.0 or >=23.4.0. Verify the installed runtime with node --version before installing.

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 through a protected process environment or the entry point's explicit environment-file option. Do not assume the working directory's .env loads automatically.
Start with help, diagnostics, or a bounded single-run workflow rather than an unattended loop.

Complete the first useful run

Enter the prepared project and run:

bash

git status --short --branch
evolver doctor
evolver cycle capabilities --json
evolver review

Step	Inspect	Decision
Workspace status	Path, branch, existing changes	Existing work identified and scope correct
doctor	Dependencies, configuration sources, identity, and connectivity	Resolve diagnostics required by the selected capability
capabilities	Collection, injection, execution, validation, recovery	Select by supported behavior rather than installed host names
review	Pending Gene candidates	Prepare material if empty; otherwise follow Review and validation

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. Verify both the shell runtime and the runtime used by the service manager.

A command is not found

Use evolver --help and the selected command group’s help to inspect entry points and required arguments. Confirm that the shell resolves the intended executable before changing configuration.

Next steps

EvoX Docs · Developers · Standalone Evolver