evolver

Evolver — WorkBuddy / CodeBuddy plugin

Self-evolution workflows for WorkBuddy, powered by Evolver (@evomap/evolver) and EvoMap.

This plugin packages Evolver as a WorkBuddy-ready workflow: a model-invoked skill, slash commands, a local status helper, and an MCP bridge to the Evolver Proxy mailbox for Genes and Capsules.

What It Does

Layer	Mechanism	Behavior
Passive recall	Skill guidance	Guides WorkBuddy to check local memory, reusable Genes, and relevant Capsules before substantive changes.
Network bridge	MCP server evolver-proxy	Exposes evolver_status, evolver_search_assets, evolver_fetch_asset, evolver_publish_asset, evolver_distill_conversation, and evolver_poll through the local EvoMap Proxy mailbox.
Quick entry	Slash commands	Adds /evolver-status, /evolver-review, and /evolver-search for common workflows.
Active control	CLI workflow	Guides WorkBuddy through evolver, evolver --review, evolver --loop, and strategy presets.
Safety boundary	Git + review	Evolver emits protocol-bound GEP prompts and audit events; WorkBuddy should not auto-apply generated output unless the user asks.

The plugin is self-contained on the WorkBuddy side. Active evolution still uses the official Evolver CLI or the local Proxy started by Evolver.

Prerequisites

• Node.js 18 or newer.
• Git.
• A git-initialized workspace for project runs.
• Optional: global Evolver CLI.

npm install -g @evomap/evolver

If the CLI is not installed globally, WorkBuddy can still explain setup. Use networked install commands only when the user approves.

Configure

Evolver works offline by default — local memory needs zero configuration: no account, no key, no node id. The steps below only matter if you also want to connect to the EvoMap network (see below).

Hub features use project-local environment variables:

A2A_HUB_URL=https://evomap.ai
A2A_NODE_ID=

About A2A_NODE_ID: Leave this blank (recommended). On first run the local Proxy registers a fresh node for you and prints a link to claim it on evomap.ai — you never paste an id or a secret here. Only fill this in to point the install at a node you already run yourself.

The MCP bridge reads the live Proxy URL and token from:

~/.evolver/settings.json

If that file is absent, it falls back to:

http://127.0.0.1:19820

Start the Proxy by running evolver once inside a git repo. The bridge never prints Proxy tokens.

Connecting to the EvoMap network (optional)

Local memory works with zero config. The network layer (searching and reusing Genes and Capsules) is opt-in. To connect:

1. Leave A2A_NODE_ID blank. Don't paste an old id and don't go hunting for a secret — blank is the intended path.

2. Install the engine and run it once inside a git repo:

   npm i -g @evomap/evolver
   evolver

   The first run registers a fresh node for you and prints a claim link.

3. Open that link while signed in to evomap.ai to claim the node. Check status any time with node scripts/evolver-status.js or /evolver-status.

If you see a different, older node than you expected, don't worry about it — just claim the current one. Reusing a specific older node requires that node's secret, which is more trouble than it's worth.

Commands

• /evolver-status checks Node, Git, Evolver CLI, git workspace status, and Proxy settings.
• /evolver-review runs evolver --review and asks WorkBuddy to explain the generated GEP output before applying anything.
• /evolver-search calls the MCP asset search workflow for Genes/Capsules that match the provided signals.

MCP Tools

• evolver_status
• evolver_search_assets
• evolver_fetch_asset
• evolver_publish_asset
• evolver_distill_conversation
• evolver_poll

Verify

From this plugin directory:

node scripts/evolver-status.js
node mcp/evolver-proxy.mjs

In normal WorkBuddy use, run /evolver-status or ask WorkBuddy to check Evolver Proxy status; when the MCP bridge is loaded it should call evolver_status first.

License

GPL-3.0-or-later, matching the upstream Evolver engine. See LICENSE.