Give the Claude Code agent a persistent, auditable evolution memory plus a bridge to the EvoMap network. Instead of re-solving the same problem every session, the agent recalls what worked before, notices improvement signals as it edits, records how each task turned out, and can search/reuse proven genes & capsules from the network — so the next session starts smarter.

Powered by the Genome Evolution Protocol (GEP) and the @evomap/evolver engine. Sibling of the Evolver Cursor plugin — same memory format, same clean-room hooks.

Status: v0.2.0 — hooks + skill + commands + MCP bridge. Works standalone (local memory) and, when the Proxy is running, exposes the EvoMap mailbox (Recipes first, then genes/capsules as fallback) as MCP tools.

Three hooks run automatically — you don't invoke them:

Memory is workspace-scoped (via a forge-resistant .evolver/workspace-id), so one project's outcomes never leak into another's session.

An MCP bridge (evolver-proxy, zero-dependency stdio server) exposes the local EvoMap Proxy mailbox as tools:

It also ships a capability-evolver skill (recall → work → record loop) and slash commands: /evolver:evolve, /evolver:search, /evolver:status, and — when @evomap/evolver is installed — /evolver:run, /evolver:solidify, /evolver:review, /evolver:sync, /evolver:distill.

/plugin marketplace add EvoMap/evolver-claude-code-plugin
/plugin install evolver@evolver

Restart Claude Code (or /reload-plugins). That's it — local memory works with zero config: no account, no key, nothing to fill in.

The network layer (searching/reusing genes & capsules) is opt-in. To connect:

1. In the plugin's config, leave "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 /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.

git clone https://github.com/EvoMap/evolver-claude-code-plugin
claude --plugin-dir ./evolver-claude-code-plugin

• Node.js ≥ 18 (hooks and the MCP bridge are Node; the bridge uses global fetch).
• Git — outcomes are derived from the project's git diff.
• For the MCP tools: the EvoMap Proxy running locally (it starts when you run the @evomap/evolver CLI once in a git repo). The hooks need none of this.

The hooks write outcomes to ~/.evolver/memory/evolution/memory_graph.jsonl (or the project's memory/evolution/ inside an evolver-managed repo). Recall and record work immediately. No account, no key, no network. The MCP tools report the Proxy is down until you start it — everything else still works.

npm install -g @evomap/evolver

Running evolver launches the local Proxy mailbox; the evolver-proxy MCP bridge then connects to it (reading the live url + auth token from ~/.evolver/settings.json) so evolver_search_assets etc. return real network assets. The engine's CLI (evolver run, evolver review, …) is surfaced as /evolver:* commands. The hooks never shell out to the engine; they just record the memory the pipeline consumes.

To record outcomes to the Hub from the Stop hook, set credentials. The hook uses Node's built-in fetch, so the API key is not exposed in process arguments:

export EVOMAP_HUB_URL="https://evomap.ai"
export EVOMAP_API_KEY="…"     # from your EvoMap node
export EVOMAP_NODE_ID="…"

• This plugin's evolver-proxy bridge is a thin, MIT, zero-dependency glue that exposes the local Proxy mailbox (the genes/capsules already synced to your machine) as MCP tools, and degrades gracefully when the Proxy is down.
• @evomap/gep-mcp-server is the standalone, Apache-licensed full GEP protocol layer — the complete gep_* tool surface for any MCP client. If you want that richer surface (beyond the mailbox proxy), add it to your MCP config directly; the two compose.
• @evomap/evolver is the GPL-licensed engine (daemon + CLI). The plugin's hooks are an independent MIT clean-room implementation that records memory in the same format the engine reads, so they interoperate when you install it.

MIT © EvoMap. The bundled hook scripts and the MCP bridge are original, clean-room implementations — not derived from the GPL-licensed @evomap/evolver source. Installing @evomap/evolver (itself GPL) to unlock the full pipeline is an independent, optional step. See LICENSE.