DSH Plugin HubDSH 插件市场

Ready22Race/dsh-team-task

Plugin插件 Native原生 ⭐ 3 MIT Subagents & Orchestration子代理与编排Productivity & Tasks效率与任务

适用于DeepSeek Harness（dsh）的团队任务：长周期多智能体任务——审查计划DAG、运行时拥有的结算、事件日志真相、常驻协调器

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

This repository is a DSH-native plugin purpose-built for managing long-horizon multi-agent tasks in DSH. It implements a structured workflow where a lead agent plans a reviewed DAG of task nodes, member agents execute individual nodes per the plan, and a resident reconciler ensures progress continues across interruptions. Prerequisites for installation include Node.js version 22.19 or newer, or 24 and above; Node 23 is explicitly noted as incompatible with DSH boot, so users should avoid that version. Pre-built output is committed to the repo, so no local build is required for installation.

The plugin solves common failure modes that plague short-burst team plugins on long tasks. It uses runtime-owned settlement, a resident reconciler that restarts stalled tasks on a timer, and a review gate that blocks downstream work until the lead approves, so early hallucinations do not poison downstream results. All events are stored in an append-only event log that acts as the single source of truth, with stale writes rejected at the log level via fence tokens. Task data is stored in the workspace’s .team-task directory, with derived snapshots and inboxes for readability only.

The plugin is released under the open MIT license, and the current v0.1 release includes full end-to-end tooling, event logging, scheduling, and review functionality. A native board UI for visualizing task progress is still on the roadmap, as are additional features like per-run cost accounting. Known limitations in the current release include that member wake-ups still require a live lead agent until upstream DSH changes are made. To start a task after installation, users simply invoke the team-task command in the DSH web interface after a restart.

这是一个专为DeepSeek Harness（DSH）打造的原生插件，用于管理跨多智能体的长周期任务。它允许首席代理规划带评审环节的有向无环图（DAG）任务流，持久化成员代理执行单个任务节点，常驻协调器会保证任务在模型故障、会话中断、DSH重启后仍能继续推进，专门适配耗时数小时而非单轮就能完成的长周期目标。

它解决了现有短周期团队插件在长任务中的常见缺陷，通过运行时自动结算、常驻定时协调、评审节点闸门、日志围栏令牌、事件日志唯一真相机制等设计，避免了任务中断、幻觉传导、过期结果等问题。用户安装后可以通过DSH命令行直接添加插件，重启DSH后即可使用，首次运行只需在对话中调用对应指令即可创建任务。

插件提供了十余个专用工具，支持任务创建、规划、派发、评审、归档全流程，所有任务事件以追加日志形式保存在工作区的 .team-task 目录下，日志是唯一信息源，派生的快照和邮箱仅用于辅助查看。插件基于MIT许可开源，当前版本已实现完整功能流，UI看板等功能仍在开发路线中。

View on GitHub在 GitHub 查看

Recommended强烈推荐 Send to your DSH发给你的 DSH 安装 
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-team-task（Ready22Race/dsh-team-task）
仓库：https://github.com/Ready22Race/dsh-team-task
本站详情页：https://www.yhbd.top/plugins/ready22race-dsh-team-task/
本站登记：类型 plugin · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 3 · 最近提交 2026-08-17 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【1 兼容性检查】
① 我这边：DSH 版本、Node 版本、操作系统、当前 profile（web / desktop）。
② 读它的 README、package.json、插件 manifest，列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对，结论只写「满足 / 不满足 / 未知」三种；不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突：命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。

【2 安全性检查】
① 仓库可信度：和上面「本站登记」是否一致；star / fork 数、创建时间、最近提交，是否归档或长期停更。
② 安装脚本：逐行看 package.json 的 preinstall / install / postinstall，以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名，立刻停下来告诉我，不要继续装。
③ 依赖：列出新增依赖，标出无人维护、或与知名包拼写近似的可疑包（typosquatting）。
④ 权限与副作用：它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限（filesystem / network / shell / clipboard 等），以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限，或权限明显超出功能所需，先停下来问我。

【3 安装】
上面两步没有「不满足」和「高危项」时才执行；用官方推荐方式安装，不要自行提权。

【4 汇报】
用表格输出：检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜，也不要替我决定。

Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH：它会先核对兼容性与安全性（逐条给「满足 / 不满足 / 未知」），确认没问题再安装，有高危项会停下来问你。框内可滚动，复制到的是完整提示词；安装命令不一定准确，发给 DSH 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意
  • Only 3 stars - very few users, little community feedback星标只有 3，几乎没人在用，遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项

Compatibility兼容性

  • DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
  • External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时（Electron / Python / Docker 等）是否齐备
  • Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突：命令名、skill / tool 重名、端口占用、重复 MCP 注册

Security安全性

  • Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致，是否归档或长期停更
  • Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
  • curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
  • Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
  • Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需（filesystem / network / shell / clipboard）
  • Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限，以及卸载与回滚方式

Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照，不能替代安全审计。

Or use CLI install (for developers)或使用命令行安装（适合开发者）

CLI Install命令行安装 

dsh plugin --profile web add @ready22race/dsh-team-task

把 Ready22Race/dsh-team-task 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

8.4 KB · 缓存于 2026-08-25 04:53:45 · 8.4 KB

team-task — long-horizon multi-agent tasks for DeepSeek Harness

npm version MIT license DeepSeek Harness plugin

A DeepSeek Harness (dsh) plugin: a lead session plans a reviewed DAG, durable members execute its nodes, and a resident reconciler keeps the task moving — across model failures, interrupted turns, and harness restarts.

Built for goals that take hours, not turns.

Why

Team plugins optimized for short bursts fail on long tasks in predictable ways. team-task's answers, in one table:

Long-task failure team-task answer
A member finishes but never calls the completion tool Runtime-owned settlement: the run settles at its idle edge regardless; tools accelerate, never gate
The lead session goes offline mid-task Resident reconciler re-kicks every task on a timer; work resumes the moment the lead returns
An early hallucination poisons downstream work Review gate: only lead approve unlocks dependents; rework sends feedback back to the same node, attempts are first-class history
A reassigned worker writes a late result Fence tokens on an append-only event log; stale fences are rejected at the log, not by etiquette
Crashed process, lost wake-ups, stranded messages The event log is the only truth; delivery is the scheduler's job and is retried at every kick
Protocol prompt tax in every request Progressive playbooks: ~8-line resident trigger; lead/member protocols load on demand via team_task_playbook

Full rationale, axioms, state machine, and the event-log-native board design: docs/design.md.

Quick start

Prerequisites: Node ^22.19 || >=24 (Node 23 fails to boot dsh).

1. Install dsh (skip if you have it):

npm i -g @deepseek-ai/dsh

2. Add the plugin — pick one:

# npm (recommended)
dsh plugin --profile web add @ready22race/dsh-team-task

# straight from GitHub (the repo ships its build output — no build step)
dsh plugin --profile web add github:Ready22Race/dsh-team-task

# from source (contributors; installs as a link to your checkout)
git clone https://github.com/Ready22Race/dsh-team-task.git
cd dsh-team-task && pnpm install && pnpm build
dsh plugin --profile web add .

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 Ready22Race/dsh-team-task 的 README.md。 在 GitHub 查看原文 →

Related相关推荐

← 上一个 Prev dsh-theme-neko 下一个 Next dsh-browser-use →