@nanmicoder/dsh-agent-teams

<p align="right"> <strong>English</strong> · <a href="./README_ZH.md">简体中文</a> </p> <p align="center"> <img src="./assets/readme/hero.svg" width="100%" alt="dsh-agent-teams turns one DeepSeek Harness session into a coordinated multi-agent team"> </p> <div align="center">

AtomGit

</div> <p align="center"> <a href="https://dshfind.com/en/plugins/NanmiCoder/dsh-agent-teams?ref=badge"><img src="https://img.shields.io/badge/recommended%20by-dshfind-FFD700?style=flat-square" alt="Recommended by dshfind"></a> <a href="https://dshfind.com/en/plugins/NanmiCoder/dsh-agent-teams?ref=badge"><img src="https://dshfind.com/api/badge/NanmiCoder/dsh-agent-teams?lang=en" alt="dshfind score"></a> <a href="https://dshfind.com/en/plugins/NanmiCoder/dsh-agent-teams?ref=badge"><img src="https://dshfind.com/api/badge/NanmiCoder/dsh-agent-teams?metric=downloads&amp;lang=en" alt="dshfind downloads"></a> </p> <p align="center"> <a href="https://www.npmjs.com/package/@nanmicoder/dsh-agent-teams"><img src="https://img.shields.io/npm/v/@nanmicoder/dsh-agent-teams?style=flat-square&amp;color=5B4CF0" alt="npm version"></a> <a href="./LICENSE"><img src="https://img.shields.io/badge/license-MIT-0B7285?style=flat-square" alt="MIT license"></a> <a href="./cordis.patch.yml"><img src="https://img.shields.io/badge/DSH-Web%20%2B%20Headless-5B4CF0?style=flat-square" alt="DSH Web and Headless"></a> </p>

One prompt. A working team.

dsh-agent-teams turns the current DeepSeek Harness session into a captain that can assemble durable sub-agents, split a goal into dependency-aware tasks, and coordinate work through direct messages.

Ask in natural language. The plugin provides the team protocol, 14 coordination tools, persistent state, an automatic shared-task scheduler, and a live Web UI—without requiring a separate workflow engine.

<p align="center"> <img src="./assets/readme/workspace.png" width="100%" alt="AgentTeams native workspace with members, task dependencies, and progress"> </p>

Releases

Latest release fixes installation on Harness 0.2.1-rc.4, 0.2.1-rc.5 (npm latest) and later releases. The plugin now declares only a minimum host (>=0.1.2-alpha.2) instead of listing tested versions, so a new Harness release no longer blocks installation. Install from npm with the exact version shown below; Git installs use the default branch. The recommended Harness host remains 0.2.1-rc.2. See the tested matrix and release notes.

Why AgentTeams?

Capability	What it changes
Captain-led delegation	The current session creates the team, assigns roles, and consolidates the final result.
Durable members	Members are continuable DSH sub-agents that can be woken for focused follow-up turns.
Dependency-aware tasks	Tasks move through explicit states and cannot be claimed before their dependencies finish.
Automatic reuse and safe takeover	Idle members claim the next ready task; reassignment revokes stale attempts before new work starts, and cold recovery retries stranded open attempts.
Direct messaging	Members send durable mailbox messages directly to teammates or the captain—no relay required.
Live activity panel	The Web UI combines segmented progress, a collapsible roster, and an interactive task DAG; running tasks show the member's model, and completed archives retain their full member and task history.
Plan before execution	Normal /agent-teams runs stage an unspawned roster and DAG first. The Web panel uses the host model catalog for member routes. Returning to chat stops the planning turn, asks what should change, and revises the same draft; discarding archives the draft, aborts the turn, and explicitly prevents automatic recreation. Only Approve & Run enables scheduling; each member starts with its first ready task.
Quality gates	Opt-in quality tasks support requirements → implementation → verification → review → integration contracts, automatic repair/re-review, and explicit resume. Scope control is a completion-time audit, not host write interception. See docs/quality-gates.md.

The conversation card and activity panel use Harness's official locale service. They follow live language changes between English and Simplified Chinese—including status labels, dynamic summaries, controls, archive markers, and accessibility text—without a page reload or a separate plugin setting.

Install and choose versions

Recommended pair: DeepSeek Harness 0.2.1-rc.2 + AgentTeams 0.1.28. The host remains an RC.

Use case	DeepSeek Harness	AgentTeams plugin
Recommended	0.2.1-rc.2	0.1.28
Preview host	0.2.1-rc.3	0.1.28
Previous recommended RC	0.2.1-rc.1, 0.2.0-rc.2, 0.1.7-rc.2	0.1.28
Legacy RC	0.1.5-rc.1, 0.1.5-rc.2, 0.1.5-rc.3	0.1.28
Retaining an older RC	0.1.2-rc.1	0.1.28
Developer Alpha testing	0.1.2-alpha.5	0.1.28
Retaining an older Alpha	0.1.2-alpha.2	0.1.28
Newer hosts	0.2.1-rc.4, 0.2.1-rc.5 and later	0.1.28

All rows except the last are the CI-tested matrix. Harness 0.2.1-rc.4 and later releases can install the plugin directly; 0.2.1-rc.5 passed the full runtime suite locally on macOS but is not yet in the CI matrix.

Desktop app

In the app sidebar, open Plugins → Add plugin. You can install directly from GitHub by pasting this repository URL into the plugin input, without a version, tag, or commit suffix:

https://github.com/NanmiCoder/dsh-agent-teams

This installs from the default branch and is available immediately after release. The equivalent shorthand is also supported:

github:NanmiCoder/dsh-agent-teams

For npm installation, enter the versioned spec @nanmicoder/[email protected]. Desktop's pnpm 11 defaults to a 24-hour minimum release age: for 24 hours after a release, a bare package name or @latest installs the previous version even when the preview shows the newest one, and the installation fails if that version is incompatible with your host. An exact version installs immediately. Changing registry mirrors does not remove this policy. GitHub access is required for the Git route; it may contain newer code than npm.

Install it, then choose Enable now. If the host asks for a restart, restart the desktop app. Do not disable compatibility checks or the global release-age policy to install the plugin.

The desktop app supplies its own Harness core and package manager. Upgrading the global CLI does not upgrade that core, and an ordinary standalone CLI cannot manage its desktop profile. The CLI carrier installed by the desktop app can manage that profile in 0.2.1-rc.2. Check the embedded core against the compatibility list. Harness 0.2.1-rc.2 is now the exact published target; its RC status is unchanged. The earlier source-only 0.2.0 prediction is no longer a support declaration. See the release migration evidence.

CLI / Web: 1. Install DeepSeek Harness

npm install --global @deepseek-ai/dsh
dsh --version

The command selects the host's npm latest; check dsh --version against the support matrix after upgrading. Alpha is opt-in: select an exact Alpha version from the table and lock all host dependencies as described in the maintenance guide.

CLI / Web: 2. Install the AgentTeams plugin

Install or upgrade from npm with an exact version (currently 0.1.28):

dsh plugin --profile web add --save-exact @nanmicoder/[email protected]

For a CLI-managed installation, replace web with your active CLI profile. Stop and restart that profile's Harness process, then refresh the browser. Installing the plugin does not upgrade Harness; the host and plugin have independent latest channels.

Alternatively, install or update from the latest GitHub default branch without a tag or commit suffix:

dsh plugin --profile web add github:NanmiCoder/dsh-agent-teams

To update, run the command again with the new version, then restart the profile; a bare package name can retain an already installed exact version. For 24 hours after a release, a bare package name or @latest installs the previous version. If a registry mirror has not synced the release, append --registry=https://registry.npmjs.org to the npm command. GitHub default-branch code may be newer than npm latest. The default branch includes the verified server, client, and type build outputs in lib/. The repository distributes these outputs so installation does not need a prepare hook or build-script approval. Source maintainers must run pnpm build and update the committed outputs whenever the source changes. Existing npm releases remain immutable.

For a manually cloned checkout, run pnpm install --frozen-lockfile and pnpm build after pulling, then restart the corresponding Harness process. Updating Git alone does not update local build output. See the maintenance guide.

For 0.1.0-* / 0.1.1-* hosts older than 0.1.2-alpha.2, keep a working pair and follow the older-version and diagnostic guide.

See the full compatibility matrix, source installation and Alpha testing guide, and verification coverage and platform limits.

Then ask for a team directly:

Use AgentTeams to review the commits after v0.5.3 from performance, security, and product perspectives. Return one consolidated report.

View teams in the workspace

Click View team in the current chat header or the team card below a reply to open the native Team collaboration tab. The entry belongs to its chat, rather than the general workspace start page.

Team and task content starts immediately: wide panes use columns and narrow panes stack them. Select a task to locate its owner; member icons open their conversations. Closing the tab does not stop the team, and its chat can reopen it. Completed teams retain their archives. Older hosts keep the activity panel.

How it works

1. For a request to use AgentTeams, the captain follows the core protocol already in its system instructions. It continues an existing team and uses agent_teams_status when current state needs checking. When no team exists, the goal becomes a staged plan for review.
2. The captain adds role-specific members backed by continuable sub-agents.
3. The goal becomes tasks with owners and explicit dependencies.
4. The shared scheduler uses real running / idle / ready state to atomically claim one ready task per idle member and wake it. An interrupted resident attempt stays parked and can resume through a direct message without losing its capability; after a cold process restart, the scheduler retries stranded open work with a fresh attempt.
5. Members update with the current attempt_id; reassignment or captain takeover revokes the old attempt and waits for the old worker to quiesce before a new attempt starts.
6. The captain presents the combined result, then archives the complete team record.

Team state is stored under <workspace>/.agent-teams/; the Web panel reads that disk truth and combines it with live sub-agent activity.

Member creation is zero-interaction by default: a member on the captain's current LLM route snapshots that provider, model, and reasoning effort, while a member on a requested alternative route snapshots the target model's default effort; later continuations restore the resolved snapshot. Only an