dsh_workflow
icetomoyo
UltraCode-style multi-agent orchestration: a generatable, savable, governable, observable, resumable workflow layer.
npm packageTypeScript3d ago
dsh-agent-teams
NanmiCoder/dsh-agent-teams
AgentTeams multi-agent teams.
Install
Add dsh-agent-teams to DeepSeek Harness
via npm
Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.
Due diligence
Before you install dsh-agent-teams
- Source of record: NanmiCoder/dsh-agent-teams — present in the community registry that DSH's own plugin market installs from.
- Licensed under MIT.
- Detected: terminal surface. Read the source before granting these.
- A listing here is not a security review. Plugins run with your agent's permissions.
What dsh-agent-teams does
dsh-agent-teams is a DeepSeek Harness plugin that turns the current session into a captain for a persistent team of coordinated sub-agents. The captain creates role-specific members, divides a goal into tasks with dependencies, and consolidates their reports. Members are continuable DSH sub-agents that can be woken for follow-up work, while direct messages are stored in durable mailboxes.
The plugin uses a shared scheduler and persisted team state. It tracks running, idle, and ready member states, atomically assigns one ready task to each idle member, and retries stranded open attempts after interruption or restart. Members update work with an attempt_id; reassignment revokes stale attempts before a new one begins. Team data is written under <workspace>/.agent-teams/, and the Web UI reads that state alongside live sub-agent activity. By default, member creation snapshots the captain's active provider, model, and reasoning effort. An explicit heterogeneous request can instead provide a member-specific provider and model.
It suits investigations, reviews, and other goals that benefit from parallel roles and a consolidated result. It is a poor fit when one agent can complete the work directly, or when multiple DSH processes must edit the same team: file state is serialised only within one DSH process. The plugin also has a terminal surface. That matters because its sub-agents perform assigned work within the current harness environment and available agent permissions, rather than in an isolated workflow service.
dsh-agent-teams documentation
Configuration
The plugin works with its defaults, or accepts configuration in a trusted profile. The stateDir value is relative to the workspace unless changed by the surrounding profile.
| Key | Example value | Meaning |
|---|---|---|
stateDir |
.agent-teams |
Directory for team state |
memberProvider |
spawn |
Sub-agent runtime backend; spawn or fork |
memberModel |
deepseek-v4 |
Default model for all members |
memberMaxDepth |
1 |
Member depth setting |
maxMembers |
8 |
Maximum member count |
memberProvider is not an LLM provider. Cross-provider routing uses the optional provider and model fields accepted by agent_teams_add_member; memberModel remains a shared default.
Commands and validation
After a source build or profile change, dsh --profile web --dump-config validates the composed profile. Start the Web UI with dsh web. Source development uses pnpm build and pnpm verify; pnpm build must be run again after source changes when using a linked local installation.
Behaviour
The current session becomes one captain and can lead one active team. Members claim ready tasks automatically when idle. A reassignment or captain takeover revokes the previous attempt_id and waits for the old worker to quiesce. Messages that cannot be delivered live remain durable and are retried at a later status boundary. The activity panel exposes roles, current work, unread messages, dependencies, and archived history from the persisted state.
Requirements and limits
An existing DeepSeek Harness installation is required. Team state is file-backed and shared through <workspace>/.agent-teams/; concurrent processes editing the same team are not coordinated. The panel reports persisted state as-is, so a model can finish work without making the expected task-state update. Defaults snapshot the captain's active provider, model, and reasoning effort; per-member model or reasoning prompts are not otherwise provided.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
Alternatives to dsh-agent-teams
63
mstar-harness
btspoony
Skill-driven harness/loop engineering workflow agent plugin.
GitHub sourceTypeScripttoday
dsh-automation
titanwings
Scheduled coding runs in fresh agent sessions with auditable history.
npm packageTypeScript2d ago
plugin-team-board
whyihaveyou
Shared multi-agent task board (create/claim/transition/query) over a Cordis service key.
GitHub sourceHTMLtoday
dsh-deep-research
omdsh-dev
Adaptive deep-research orchestrator built on the official workflow engine.
GitHub sourceTypeScript4d ago
dsh-science
biociao
Claude Science-style research workbench: ReAct research-loop engine (research_* tools), versioned artifacts with provenance (artifact_* tools), and 10 science skills for genomics/pathogens/bioinformatics.
npm packageJavaScripttoday