ZekaiShi/evo-subagent

English | 简体中文

Downloads

Cumulative npm download data since the first release, refreshed automatically every day. DSH Market ranks plugins using npm downloads, so this is the closest public adoption signal; it cannot distinguish marketplace installs from direct npm installs.

evo-subagent is a DeepSeek Harness plugin for predictable subagent routing and project-scoped evolution.

It maps stable agent roles to registered provider/model pairs, remembers verified commands and lessons for each role, and keeps every project's agent knowledge isolated.

Features

• Route each agent_key through a same-named Markdown binding.
• Validate the exact provider/model pair before creating a child agent.
• Maintain per-agent prefercmd.md and memory.md knowledge files.
• Isolate bindings and evolution data by project workspace.
• Support fresh spawn children and context-aware fork children.
• Fall back to DSH's native model inheritance when no binding exists.
• Store no API keys, endpoints, credentials, or provider definitions.

Installation

Requires DeepSeek Harness 0.1.5-rc.3 or newer and Node.js >=24.2.0.

dsh plugin add evo-subagent

Quick start

1. Open Settings → Plugins and expand evo-subagent.
2. Select a workspace and add a built-in role, or place a custom binding in its agents/ directory.
3. Choose a registered provider/model pair for each custom binding.
4. Expand an agent to review its prefercmd.md and memory.md evolution files.

Download the MP4 tutorial

Changelog

New entries are added at the top for every maintained release.

0.7.0 — 2026-09-27

• Refreshed the development validation baseline to DeepSeek Harness 0.1.5-rc.3.
• Bundled three DSH Agent Skills for route diagnosis, memory review, and delegation guidance. They appear in the DSH skill catalog when the skill service is available.
• Confirmed the subagent routing seam remains unchanged.

0.6.1 — 2026-09-19

• Refreshed the development validation baseline to DeepSeek Harness 0.1.5-rc.2.
• Rechecked routing, workspace evolution, and settings tests without changing plugin behavior.

0.6.0 — 2026-09-12

• Added compatibility with DeepSeek Harness 0.1.5-rc.1 and Cordis 4.0.2.
• Raised the required Node.js runtime to >=24.2.0 for the updated DSH CLI.
• Revalidated routing, workspace evolution, and settings behavior on the new runtime.

Agent bindings

Create an agents/ directory in the project and add one Markdown file per role. The filename stem becomes the agent_key.

project/
├─ agents/
│  ├─ code-reviewer.md
│  └─ researcher.md
└─ .evo_subagent/
   └─ evolution/

Each binding begins with a strict front matter block:

---
provider: deepseek-official
model: deepseek-v4-flash
---

# Code reviewer
Optional role notes may follow.

The provider and model must already be registered. Matching is exact and case-sensitive.

Call the plugin tool with the corresponding key:

{
  "agent_key": "code-reviewer",
  "description": "Review the implementation",
  "prompt": "Report correctness, security, and test coverage issues.",
  "run_in_background": false
}

Built-in roles

Three templates are included:

agent_key	Role
code-reviewer	Severity-ranked code review
researcher	Evidence-backed investigation
wps-worker	Office document production

A project binding with the same agent_key overrides its built-in template.

Bundled Agent Skills

Installing this plugin also registers three optional DSH-compatible skills in the DSH skill catalog. They guide the parent agent; they are not additional subagent roles.

Skill	Purpose
/evo-route-doctor	Diagnose an unexpected route or invalid registered provider/model pair.
/evo-memory-review	Review a role's prefercmd.md and memory.md for stale or conflicting knowledge.
/evo-delegation-guide	Choose an existing role and prepare a scoped subagent task.

DSH needs its skill registry and skill tool enabled for these entries to appear. A project-specific skill with the same name can override a bundled entry. The skill files are also included in the npm package under skills/.

Evolution

Each project stores role-specific knowledge under:

.evo_subagent/evolution/<agent_key>/prefercmd.md
.evo_subagent/evolution/<agent_key>/memory.md

• prefercmd.md records commands that have been verified to work.
• memory.md records reusable lessons and failures to avoid.

Foreground subagents receive a bounded knowledge block. They can return new entries with:

[[EVOLUTION]]
prefercmd:
- pnpm test
memory:
- Do not use --force in CI.
[[/EVOLUTION]]

Entries are deduplicated and bounded. Prefix an entry with ! to keep it at highest priority, or ? to make it compressible when the context budget is tight.

Legacy .smart_subagent/evolution data remains a read-only fallback and is copied to the new location on the next save.

Workspace management

The plugin settings card groups agents by project and lets users:

• view or collapse workspace agent lists;
• edit a custom binding's registered provider/model route;
• add a built-in role to a workspace by copying its template;
• bind one workspace-root AGENTS.md as the Main agent;
• inspect and edit each agent's evolution files.

Main-agent evolution is stored under .evo_subagent/evolution/main/. Binding and unbinding only changes the plugin-managed instruction block in AGENTS.md.

Tool fields

Field	Required	Description
agent_key	Yes	Binding filename without .md.
description	Yes	Short task label.
prompt	Yes	Complete task for the child agent.
run_in_background	No	Defaults to true; use false to collect evolution output.

Routing behavior

1. Resolve <agent_key>.md safely.
2. Parse its fenced provider and model fields.
3. Verify both values against the live model registry.
4. Start the child through the selected spawn or fork provider.

Invalid bindings fail before a child is created. Missing bindings preserve native DSH inheritance unless a built-in template matches.

Development

Requires Node.js 24.2 or newer.

npm test
npm run check
npm pack --dry-run

License

MIT