dshbase

插件目录 / Knowledge / evo-subagent

evo-subagent

已验证 · 实测可装 ZekaiShi

✓ 持续维护 3 位贡献者 基于 4 个官方 DSH 包

查看 GitHub ↗ ← 返回插件目录

3Stars
0Forks
0未关闭 issue
—语言
2026-08-24最近推送
跨平台平台

功能简介

Unified DeepSeek Harness plugin: role-based subagent routing + per-agent evolution (prefercmd/memory as knowledge allow/deny lists), so repeated tasks start from proven commands and save tokens. Unified subagent routing and evolution: prefercmd/memory serve as knowledge allow/deny lists, saving tokens.

✅
我们的评价
可用 — 实测通过,早期项目

Unified DeepSeek Harness plugin: role-based subagent routing + per-agent evolution (prefercmd/memory as knowledge allow/deny lists), so repeated tasks start from proven commands and save tokens. Unified subagent routing and evolution: prefercmd/memory serve as knowledge allow/deny lists, saving tokens. 实测能干净安装、正常启动。早期项目,但功能可用。

「已验证」表示我们的自动化 CI 在干净 profile 里实际执行了 dsh plugin add 并启动成功——仅此而已。功能描述与版本兼容性均为作者声明。这不是安全审计,也不代表对第三方代码的背书。

README

evo-subagent

evo-subagent — Route. Remember. Evolve.

English | 简体中文

npm version
license
Node.js

Downloads

Cumulative npm 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

dsh plugin add evo-subagent

Quick start

Open and manage evo-subagent in DSH

  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

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.

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 22 or newer.

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

License

MIT

安装

🧩 让 Agent 自动装(推荐)

装一次目录插件,之后本站所有插件都能让 DeepSeek Harness 自动找、自动装:

dsh plugin add dshbase-catalog

然后对 agent 说「帮我装 evo-subagent」,它会在目录里找到并自动安装。文档:dshbase-catalog · 已验证场景包。

该插件是 GitHub 源码(未发 npm)——直接从仓库装:

Web profile:

dsh plugin --profile web add github:ZekaiShi/evo-subagent

Headless(CLI)profile:

dsh plugin --profile headless add github:ZekaiShi/evo-subagent

实测报告

验证通过:从 GitHub 源码完成 L1 安装 + L2 加载 + L3 运行(dsh 0.1.0-rc.6)。

安全:尚未扫描——我们的每日静态扫描将很快覆盖它。

分享徽章

Knowledge 里更多

浏览全部 7819 个插件 →