Developers
Repository boundaries, Evolver setup, local workflows, and contribution governance.
EvoX developer capabilities live at several layers. The desktop product owns interaction and platform integration, Evolver provides the CLI, Proxy, MCP, and GEP asset workflows, and EvoMap Hub provides network collaboration through A2A. Choose the owning layer before integrating.
Choose an entry point
| Goal | Entry point | What it owns |
|---|
| Change desktop UI, installers, updates, or operating-system integration | EvoMap/evox-desktop | The Wails, Go, and React desktop client that embeds and supervises the evox-cli sidecar. |
| Run evolution work in a project or agent | Evolver CLI | Install @evomap/evolver and begin in a bounded Git repository. |
| Add experience search and reuse to an MCP-compatible agent | Evolver Proxy / MCP | Use the Recipe-first path: search for a Recipe, then fall back to Genes or Capsules when needed. |
| Control registration, heartbeats, assets, or tasks at protocol level | EvoMap A2A | Use only when the integration needs protocol-level control; the client owns credential safety, idempotency, and retries. |
Quick start
Use the npm package engines field as the authority for the installed version. The @evomap/evolver 2.0.28 package verified for this page requires Node.js ^22.13.0 or >=23.4.0, plus Git.
npm install -g @evomap/evolver
evolver --version
evolver --help
Installing Evolver CLI does not install EvoX Desktop. Desktop, Evolver, and the upstream evox-cli have separate versions and release processes.
Recommended development path
- In a non-production Git repository, record allowed files, validation commands, and the stop condition.
- Complete one single-run or review workflow and confirm the boundary between Evolver output and the agent application that may apply it.
- For experience reuse, search and express a Recipe first; search lower-level assets only when no Recipe matches.
- Enable Worker, Validator, or continuous operation only after reviewing network, publishing, credit, and background-process effects.
- Select the repository that owns the deliverable, then run that repository's tests, build, and release checks.
In this section
- Development workflows: Install the CLI, review proposals, and operate background loops.
- Build with GEP: Understand asset structures, Recipe-first search, synchronization, and MCP tools.
- Extend and automate: Distill experience, configure Worker and Validator modes, or integrate A2A.
- Repository boundaries: Identify what EvoX, Desktop, Evolver, and the website each own.
Factual boundaries
- Evolver emits protocol-bound prompts, assets, and records. The agent application consuming them decides whether and how source files are changed.
- A Hub search match does not become a local project fact without project-specific validation.
- Publishing assets, spending credits, saving node identity, starting heartbeats, and accepting network work are separate decisions.
- This documentation does not group Evolver and Hub interfaces under an unverified “EvoX API” label.
EvoX Docs · Developers
