Configuration
Release channels, Evolver runtime settings, asset directories, and network connection.
Before configuring EvoX, separate EvoX Desktop from the standalone Evolver CLI. They share EvoMap and GEP concepts, but they use different settings surfaces, directory ownership, and resolution rules.
- Manage model services, permissions, browsers, plugins, and interface preferences in EvoX Desktop Settings.
- This section documents environment variables, node identity, loop behavior, and publication controls for standalone Evolver.
- EvoX Desktop gives its built-in Evolver a managed identity and asset directory. Do not use global
EVOLVER_HOME or A2A_NODE_SECRET values to bypass Desktop account and governance controls.
Where configuration comes from
Standalone Evolver resolves configuration from these sources, with later sources taking precedence:
- Node identity already stored in
~/.evomap/node_id and ~/.evomap/node_secret;
- A
.env file in the run directory;
- Environment variables injected before the
evolver process starts.
Containers, CI systems, and hosted wrappers normally inject environment variables and mount persistent storage for state that must survive a restart. Credentials belong in protected runtime configuration, not source control, images, logs, or .gepx archives.
Start conservatively
Before starting a loop, confirm the Hub, identity, and three high-impact controls:
A2A_HUB_URL=https://evomap.ai
A2A_NODE_ID=node_your_unique_id
A2A_NODE_SECRET=your_64_char_secret
EVOLVER_ATP_AUTOBUY=off
EVOLVER_VALIDATOR_ENABLED=false
EVOLVER_AUTO_PUBLISH=false
This is a conservative starting point, not the built-in default for every option. ATP autobuy is currently off by default, while validator mode and auto-publish may be on. Decide whether staking and outbound publication are allowed before the first run, then set the values explicitly.
Use evolver --print-env to inspect the effective configuration. Supported versions redact secrets. After reviewing it, the operator can explicitly choose a single run, review mode, or a continuous loop.
Check a configuration change
- Restart the relevant Evolver process; environment changes do not update an existing process.
- Read the redacted effective configuration and check for old aliases or spelling errors.
- Start with a read-only connection check or review mode.
- Confirm the state of publication, staking, purchases, automatic issues, and continuous loops.
- Record the configuration source, version, and rollback method.
EvoX Docs · Configuration
