Choose a task that benefits from explicit branches before creating a team. For example, separate source discovery, API comparison, and test planning can be concurrent, while a final integration step depends on their outputs. Tell the captain what a satisfactory final artifact is and which constraints apply. The presence of dependency declarations does not replace a human decision about scope, sensitive data, or whether parallel agent work is worth the additional context and cost.
BundleAgents / Collaborationv0.1.0Developer Preview
DSH Agent Teams
A DeepSeek Harness Web Bundle for natural-language multi-agent teams with a current-session captain, resumable members, dependency-aware tasks, direct messages, and a live activity panel.
197 repository starsMIT Updated Aug 14, 2026
Review snapshot
- Manifest
- Passed
- Install
- Not tested
- Runtime
- Not tested
Static compatibility snapshot dated 2026-08-14; install and runtime remain independent checks.
Install / upstream documentation
Use the pinned upstream documentation
No version-pinned install command is recorded for this listing. Use the pinned README as the source of truth; AgentPlugin.net does not invent missing steps, Profiles, or recovery instructions.
The pinned README shows a GitHub install command, but its repository reference is not immutable. This directory does not invent a commit-pinned CLI form; review the fixed README and package before following upstream installation guidance.
Source: Pinned upstream README at aace29cPlugin brief
What DSH Agent Teams adds to DeepSeek Harness
DSH Agent Teams is a DeepSeek Harness plugin for turning one conversation into a managed multi-agent team. The upstream README describes the current session agent as the captain, with members that can keep a conversation state, tasks that declare dependencies, and direct member-to-member messaging rather than mandatory captain relays. In the Web GUI, it also advertises a real-time activity panel. The intended interaction is natural language: a user asks the assistant to use AgentTeams for a goal, then the model follows the plugin’s prompt and tool protocol to create, coordinate, collect, and report from a team.
This is more than a generic request to “use subagents.” The pinned source presents a specific team lifecycle: create a team, recruit members, decompose work and its dependencies, claim and wake members, poll results, report, then delete the active team while retaining an archive. That structure can help with research or implementation tasks that have genuinely independent investigations. It also adds orchestration overhead, so it is not automatically a better choice for a short single-threaded question or a task with unclear ownership.
The patch reveals an important local-state detail. It inserts the dsh-agent-teams package with a default stateDir of .agent-teams, placing team.json and inbox/*.jsonl mailboxes under a session workspace. The default member provider is spawn, with fork named as another available provider in the patch comment. Team state and messages can therefore become project artifacts. Review, ignore, retain, or remove that state deliberately; do not assume a collaboration panel is purely ephemeral or that it is safe to add to source control.
The package is a DSH Bundle, not merely a prompt template. Its package manifest declares a Cordis patch and Web client injections, and the patch says it registers agent_teams_* tools into the shared registry and usage content into the global system prompt. This static evidence establishes its integration surface but does not prove the tool semantics, team isolation, or Web panel behaviour in a live profile. DSH is a developer-preview ecosystem; the peer dependencies target its 0.0.1-rc.1 family, while the catalog has not executed this release.
Evaluation workflow
Evaluate DSH Agent Teams with clear boundaries
Inspect the session workspace before and after use. The pinned patch documents .agent-teams as the default storage location for team state and JSONL inboxes. Add it to an ignore policy only after determining whether it contains material you need for audit or recovery; never blindly commit task messages, prompts, repository paths, or agent outputs to a shared repository.
Use the activity panel as coordination visibility, not as authorization. Members may send messages directly and wake one another, so the captain is not necessarily the only route for work. Review task assignments and eventual outputs, especially any code, shell instructions, or external claims. A task being marked complete is a workflow signal, not evidence that the branch was tested, secure, or ready to merge.
End the evaluation cleanly. The README describes reporting and deleting the team while retaining an archive. Confirm what deletion and archival mean in the version you install, stop members before changing profile configuration, and check the pinned source when an update changes tool names or UI behaviour. AgentPlugin.net did not validate a real multi-agent lifecycle, so use a disposable workspace for the first run.
Verification ledger
Evidence, not installation claims
Manifest
PassedPinned package.json declares dsh.bundle.patch and Web client injection. The patch inserts dsh-agent-teams as agent-teams with .agent-teams stateDir and spawn memberProvider.
Checked Aug 14, 2026
Install
Not testedNo package installation was run in a DSH profile.
Runtime
Not testedNo team creation, member communication, workspace state, or Web activity panel smoke test was performed.
| Layer | Result | What was checked |
|---|---|---|
| Manifest | Passed | Pinned package.json declares dsh.bundle.patch and Web client injection. The patch inserts dsh-agent-teams as agent-teams with .agent-teams stateDir and spawn memberProvider.[Aug 14, 2026] |
| Install | Not tested | No package installation was run in a DSH profile. |
| Runtime | Not tested | No team creation, member communication, workspace state, or Web activity panel smoke test was performed. |
Source or manifest review can be recorded while Install and Runtime remain not-tested. Treat these as separate verification layers.
Execution surface
Prepare, build, and code-execution review
prepare
not recorded
No review record is available for this execution surface. Inspect the upstream repository before running it.
build
notice recorded
The source package has TypeScript and tsdown build steps. Installing from source or modifying the package executes a build workflow.
code execution
review recorded
The Bundle registers team-management tools and can coordinate multiple agent members. Review every resulting command, code change, and external action.
configuration
review recorded
Default .agent-teams workspace state contains team and mailbox data. Keep it out of commits or shared locations unless it has been intentionally reviewed.
network
notice recorded
Member agents may perform the network-enabled work available to their DSH environment; the Bundle does not itself make external results trustworthy.
Third-party code can execute during dependency preparation, build, or runtime. Read the upstream source and its changes before use.
Declared scope
Capabilities and prerequisites
Capabilities
- Create a team led by the current session agent
- Spawn or fork resumable member subagents
- Track tasks with declared dependencies
- Exchange direct mailbox messages and show a Web activity tree
Prerequisites
- DeepSeek Harness Web profile
- Node.js ^22.19 or >=24 and pnpm 11, as stated by upstream
- A task suitable for multi-agent decomposition
- A workspace where .agent-teams state files are acceptable
Frequently asked questions
DSH Agent Teams FAQ
What does DSH Agent Teams add?
It adds a team-oriented workflow to DeepSeek Harness: a current-session captain, resumable members, dependency-aware tasks, direct mailboxes, and a Web activity tree according to the upstream README.
Does every task need Agent Teams?
No. The plugin is best evaluated on work that can be decomposed into independently useful roles. For simple sequential tasks, team setup and coordination can be unnecessary overhead.
Where does team state live?
The pinned Cordis patch documents a default .agent-teams directory under the session workspace, with team.json and inbox JSONL files. Treat those as potentially sensitive workspace artifacts.
Can team members message each other directly?
That is a central project claim: the README describes direct mailbox delivery and wake-ups without routing every message through the captain.
Is DSH Agent Teams a DSH Bundle?
Yes. The package declares dsh.bundle.patch, and the reviewed patch inserts the agent-teams row with its state directory and member-provider configuration.
Has AgentPlugin.net run a team in DeepSeek Harness?
No. This entry is based on static source evidence. Installation, tools, member spawning, message delivery, and the Web panel are all marked not tested.