Evolver for DeepSeek Harness

Give dsh agents a persistent, auditable evolution memory and a native bridge to the EvoMap network. The plugin injects one reusable strategy behind each prompt it fits, observes successful edits, records every turn result, and lets agents search, reuse, report, distill, and publish evolution assets without an MCP hop.

Powered by the Genome Evolution Protocol and @evomap/evolver.

Status: pre-release 0.1.0. Local memory, commands, Skill, and the current Proxy-backed asset loop are implemented. The npm package is published only when the first matching release tag is created.

What it does

Seam	dsh event	Behaviour
Asset priming	agent/pre-step, once per turn	Recalls from the Proxy in a single /asset/fetch call carrying that turn's own prompt — only the text the person typed — and injects the strategy of the highest-scoring asset that came back carrying between four and eight steps — recall bypasses the Hub's own thin-gene filter, so both bounds are applied here — announced by the asset's short title rather than its hash, falling back to its description when the Hub's title is a truncated fragment. The hash appears once, on the line that asks for the outcome, because that call needs it. A lookup slower than the wait budget is injected into the next step instead of holding the current one. Assets already injected in this session are skipped.
Signal detection	successful tools/result for write, edit, or str_replace_editor	Tags the turn with improvement signals and injects one bounded notice per file/signal set.
Reuse feedback	session/event → turn/end	Reports each strategy injected during that turn to the Proxy with the turn's outcome, marked as automatic and unconfirmed. Injected asset ids are written to ~/.evolver/state/ as they are injected and read back at report time, so a report survives the process dying in between. Each report names the asset it is about and carries a per-turn id the Hub hashes with it to recognise a retry — a report without one is rejected outright — and a later correction carries its own, so it is not dismissed as that retry. Each verdict is written twice: to the Proxy, and as a value.reuse_hit / value.reuse_outcome root event in ~/.evomap/evolution/root_events.jsonl. The local write is the one that closes the loop — the actuator that re-orders future candidates reads root events, not the Hub. An asset the model reported itself with evolver_asset_reuse_result is left alone.
Verdict correction	agent/pre-step	When the prompt that opens a later turn in the same session plainly says the last answer did not hold, the verdicts already sent for that session are revised to failed — each asset at most once, since the Hub counts every report it receives.
Capture	session/event → turn/end	Collects staged, unstaged, and untracked work asynchronously; records the real turn outcome once; drains at session/flush.
Tools	ctx.tools.register	Connects directly to the local Evolver Proxy for status, search, fetch, reuse feedback, distillation, publication, and mailbox polling.
Skill	ctx.skills.registerProvider	Provides capability-evolver, the reuse → verify → record loop.
Commands	ctx.commands.register	Adds /evolver-status, /evolver-search, /evolver-run, /evolver-evolve, /evolver-distill, /evolver-solidify, /evolver-review, and /evolver-sync.

Every session resolves its own session.header.cwd; a long-lived Web process can serve multiple repositories without sharing their memory or diffs. Memory entries include the workspace, session, turn, turn reason, and diff fingerprint.

Install

Until the first npm release, install from a pinned repository commit:

dsh plugin --profile web add -w github:EvoMap/evolver-dsh-plugin#<sha40>

Or install from a local checkout:

dsh plugin --profile web add -w ./

After @evomap/dsh-evolver@0.1.0 is published:

dsh plugin --profile web add -w @evomap/dsh-evolver

The package declares dsh.bundle, so dsh adds it to the selected profile without manual cordis.patch.yml edits. Verify and boot the profile:

dsh --profile web --dump-config | grep -A2 'dsh-evolver'
dsh --profile web

Connect the EvoMap network

Local memory works without an account or network connection. To enable network assets:

1. Install the engine: npm install -g @evomap/evolver.
2. Run evolver once inside a git repository. It starts the local Proxy and prints a claim link for a fresh node.
3. Open the claim link while signed in to evomap.ai. The /evolver-status command reports a pending link without adding it to the model context. Set claimNudgeEnabled: true only if periodic reminders are desired.
4. Run /evolver-status to confirm the Proxy and node state.

The Proxy is a separate loopback process. This plugin never spawns it and never sends its bearer token to a non-loopback address.

Native tools

Tool	Purpose
evolver_status	Inspect Proxy and mailbox state.
evolver_search_assets	Search Genes, Capsules, Evolution Events, or AntiGenes by signals or text.
evolver_fetch_asset	Fetch reusable summary, strategy, validation, or content.
evolver_asset_reuse_result	Report the verified reuse outcome and credit the author.
evolver_distill_conversation	Persist a verified conversation lesson locally and optionally submit it.
evolver_publish_asset	Queue Genes or Capsules for Hub review.
evolver_poll	Read inbound mailbox messages without consuming them.
evolver_ack	Retire processed mailbox messages by id.

The current local Proxy does not expose Recipe search or expression routes. Asset search is therefore the supported fallback in this release; Recipe-first support belongs in a future plugin release after those Proxy routes ship.

Modes

Local memory

The default mode needs only git. Outcomes go to an existing project-managed memory/evolution/memory_graph.jsonl, otherwise to ~/.evolver/memory/evolution/memory_graph.jsonl. Unsafe project symlinks are rejected.

Per-workspace bookkeeping — the workspace id and the capture state — lives under ~/.evolver/state/, keyed by a hash of the workspace root. Nothing is written into your repository, so there is no .evolver/ directory to gitignore. A workspace-id left in a repository by an earlier version is still honoured and copied forward on first use.

Proxy-backed network

Running evolver starts the Proxy. The plugin reads its rotating loopback URL and token from ~/.evolver/settings.json on every request. If the Proxy is unavailable, native tools return an actionable error while local memory continues working.

Direct Hub outcome recording

Set all three values to additionally post turn outcomes to the Hub:

export EVOMAP_HUB_URL="https://evomap.ai"
export EVOMAP_API_KEY="…"
export EVOMAP_NODE_ID="…"

Remote Hub recording requires HTTPS. Loopback HTTP remains available for local testing. Local memory is written before the network attempt.

Configuration

The plugin exports a validated Schemastery Config; invalid values fail at load time.

Field	Default	Meaning
projectDir	session cwd, then $DSH_PROJECT_DIR, then process cwd	Explicitly override workspace resolution for every session.
proxyPort	$EVOMAP_PROXY_PORT, then 19820	Loopback Proxy fallback port.
editToolNames	['write', 'edit', 'str_replace_editor']	Successful edit tools scanned for signals.
gitTimeoutMs	5000	Deadline for each asynchronous git command.
gitMaxBufferBytes	10485760	Maximum stdout retained from one git command.
proxyTimeoutMs	8000	Native Proxy tool deadline.
hubTimeoutMs	8000	Direct outcome-recording deadline.
assetPrimeEnabled	true	Look one reusable strategy up per turn and inject it behind that turn's prompt.
assetPrimeMinSimilarity	0.3	Lowest similarity worth injecting; among the recalled assets that clear it, the highest-scoring one with a strategy is used. The score swings with phrasing, so the floor is low: measured on a live Hub, one React question scored 0.88 and 0.40 depending on wording, while boilerplate and off-topic hits sat at 0.19–0.22. A Proxy that reports no score is not filtered.
assetPrimeWaitMs	6000	How long a step may wait for that lookup, so a strategy lands behind the prompt it was selected for rather than after the model has already chosen what to do. The budget was sized for the two serial round trips recall replaced, where the lookup took 4.8s–9.4s with a 5.1s median over six prompts against a live Hub; one call should sit well inside it, and the default stays until the single-call cost has been measured the same way. Past it the step proceeds and the strategy, when it lands, is injected into the next step.
assetPrimeTimeoutMs	8000	Deadline for the recall call. A cold Hub query runs into seconds, so this is generous; assetPrimeWaitMs is what protects the response.
claimNudgeEnabled	false	Inject a trusted pending claim link behind the first prompt. /evolver-status remains available when off.
claimNudgeTtlMs	43200000	Minimum interval between enabled pending-claim notices.
captureDedupeTtlMs	86400000	Durable duplicate-capture suppression window.
captureLockStaleMs	60000	Age after which a crash-left capture lock may be recovered.
captureLockWaitMs	65000	Maximum lock wait; must be greater than captureLockStaleMs.
untrackedHashMaxBytes	1048576	Maximum sampled bytes used to fingerprint one untracked file.

Environment overrides: MEMORY_GRAPH_PATH, EVOLVER_WORKSPACE_ID, EVOLVER_HOOK_LOG_DIR, EVOLVER_SESSION_STATE_DIR, EVOMAP_PROXY_PORT, EVOMAP_HUB_URL / A2A_HUB_URL, EVOMAP_API_KEY / A2A_NODE_SECRET, and EVOMAP_NODE_ID / A2A_NODE_ID.

Requirements

• Node.js 22.13 or newer.
• Git for turn capture.
• dsh 0.1.5 or newer. The plugin declares no upper bound: the host provides dsh-llm, dsh-tools, and dsh-skill at runtime, and CI runs the suite daily against the newest published dsh so an incompatible release is caught before users upgrade into it.
• Optional network tools: a local Proxy from @evomap/evolver 2.0.39 or newer, which is the first release whose /asset/fetch recalls by text. When an older evolver is on PATH, the first step of a session carries a notice to upgrade it, at most once a day per installed version.

In a non-git directory the plugin emits one notice per directory, does not create workspace state, and records nothing. Network strategies are still injected there — they do not depend on git.

Development

npm ci
npm test
npm pack --dry-run

CI validates Node 22 and 24, the oldest supported dsh line, and the newest published dsh. The release workflow publishes only a tag whose version matches package.json; this task does not create that tag.

License

MIT © EvoMap.