Inspect, generate, and run evolution workflows in your terminal
Evolver CLI
Manage evolution material, reusable assets, and audit records from your terminal. Inspect runner capabilities before choosing an execution flow.
$ evolver cycle capabilities
codex: ingest=supported inject=supported
execute=unsupported verify=unsupported resume=unsupported
Evolver · example output
Work in a local project
Run Evolver against a bounded repository or agent workflow and keep relevant context close to the task.
Stay in control
Choose strategy, loops, file boundaries, validation, publishing, and credit behavior before the run.
Export experience assets
Inspect local assets and export Genes, Capsules, provenance, and sync metadata for migration.
Quickstart
Get started with Evolver CLI
Install the package, verify the command, and begin in a non-production project.
Install Evolver CLI
Evolver requires Node.js ^22.13.0 or >=23.4.0 and Git. Record the installed version and check the target package’s engines before upgrading.
npm install -g @evomap/evolverVerify the installation
Confirm the command is available before opening a project or enabling network behavior.
evolver --version evolver --helpOpen a bounded project
Choose a test repository, document the allowed files and commands, and remove production credentials.
cd <your-test-project>Inspect execution capabilities
Inspect ingestion, injection, execution, verification, and resumption separately. Built-in autonomous Claude, Codex, and Cursor execution is disabled; Gemini and the independent llm file executor are experimental. Read the development guide before configuring a finite flow in an isolated repository.
evolver cycle capabilities --json
See what Evolver CLI can do
Inspect runtime capabilities
Check each host’s material ingestion, context injection, execution, verification, and resumption status. A working integration does not enable every stage.
$ evolver cycle capabilities --jsoninspect input · retain records · define boundaries
Preview skill material
Preview skill generation using an actual Gene ID. Inspect the content and destination before explicitly writing through the skill workflow.
$ evolver skill fetch --asset <gene-id>inspect input · retain records · define boundaries
Review candidate Genes
List auto-distilled Genes awaiting review and inspect their provenance, prerequisites, and strategy. Asset approval, edits, tests, and publication are separate decisions.
$ evolver reviewinspect input · retain records · define boundaries
Build terminal workflows around Evolver
Export a portable evolution archive
Evolver CLI exports Genes, Capsules, provenance, and sync metadata as a JSON Portable Evolution Archive. It is not a full event or memory backup. Inspect its contents and exclude credentials before transfer.
evolver sync --export backup.gepxUse Evolver CLI in automation
For CI or scheduled execution, pin the tool version, inject identity securely, set hard runtime and change limits, keep publishing and spending explicit, and preserve logs and artifacts for review.