dsh-agent-team-gui
toolclub/dsh-agent-team-gui
Global persistent agent squads with per-agent model/tool policies: manage them in Settings, select and toggle one per conversation, then collaborate on normal sends in a fixed or model-planned order.
Install
Add dsh-agent-team-gui to DeepSeek Harness
via GitHub · GitHub source
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.
What happened when we ran it
Installs, but needs a build approved first
pnpm refuses to run a package's build script until it is allowlisted. Add the key pnpm prints to allowBuilds in the profile's pnpm-workspace.yaml, then run the command again.
Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run yesterday.
Due diligence
Before you install dsh-agent-team-gui
- Source of record: toolclub/dsh-agent-team-gui — 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.
The AI take
What it is — Provides persistent multi-model agent teams for DeepSeek Harness. Manage in settings, select and toggle one per conversation.
Who it is for — 适合在需要多模型协作完成任务的对话中使用此插件。 如果只需要单模型直接回复的用户无需此插件,因为它主要针对持久团队管理。
Watch out — Requires manual build permission for the Git dependency. Sandbox test shows the plugin can be installed only after authorizing the build script. No other obvious issues found.
The verdict — I would install it if I need persistent multi-model team management with dynamic planning, but only after manually allowing the build, as the value is in reusable agent squads.
Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.
What dsh-agent-team-gui does

dsh-agent-team-gui is a DeepSeek Harness plugin that manages persistent agent teams and runs them from the normal conversation composer. DeepSeek Harness loads the plugin in the Web profile, where it adds Teams and Members settings plus Team, Solo, and Inherited conversation modes. DeepSeek Harness uses the selected conversation's provider/model route for a bounded, tool-free planner when dynamic planning is enabled. The planner reads member roles and returns structured assignments and an acyclic dependency graph; ready members then run concurrently up to maxConcurrency, while dependent members receive bounded structured handoffs. Fixed order instead runs members serially. Team runs write durable history containing plans, stages, outputs, errors, timings, retries, review or repair rounds, and official token-usage coverage.
Each member can have its own model route, role prompt, fallback route, token limit, and tool policy. The plugin supports Always, Smart, and Manual activation, all-member or adaptive selection, foreground or background work, and optional resilience, budget, and quality-gate controls. Members can be granted terminal tools, so the terminal surface reaches whatever terminal operations those policies permit; review permissions before running a team.
dsh-agent-team-gui suits developers who repeatedly coordinate planners, implementers, reviewers, or specialists across conversations. It is a poor fit when a normal single-agent send is sufficient, or when the required DeepSeek Harness Web profile, supported Node.js version, pnpm, and configured provider/model route are unavailable. Node.js 23 is unsupported, and Git installation may require authorising the package's prepare build.
dsh-agent-team-gui documentation
Configuring dsh-agent-team-gui
DeepSeek Harness loads dsh-agent-team-gui in the Web profile. Open Settings → Members to define reusable members with a provider/model route, role prompt, optional fallback route, token limit, and permitted tools. In Settings → Teams, combine members and choose:
- dynamic planning or
Fixed order; Always,Smart, orManualactivation;All membersorAdaptiveselection;- foreground or background responses;
- optional resilience, budget, and quality-gate controls.
The conversation control beside the normal composer supports Team, Solo, and Inherited. A project default can be followed through Inherited; a queued Team or Solo selection applies to the next eligible message only.
How dsh-agent-team-gui behaves
Dynamic planning uses the active conversation's provider/model route in a bounded, tool-free planner child. The planner receives member roles and returns structured assignments with an acyclic dependency graph. Invalid, cyclic, or unavailable plans fall back to deterministic role-scoped assignments. Ready nodes run up to maxConcurrency; dependent members receive bounded structured handoffs, while complete output remains in durable run history. Fixed order bypasses DAG planning. A quality gate can request up to two repairs from a named repair owner.
The Team runs view exposes plans, stages, members, review or repair rounds, outputs, errors, timings, retries, and official token coverage. Conversation states remain available after refresh, Host startup, and live reconnect.
Commands and package build
Use dsh --profile web --dump-config to inspect the composed configuration; its output should contain the dsh-agent-team-gui bundle layer and an agent-team-gui row. Git dependencies run the repository's prepare build. With pnpm 10 or later, authorise only this package by adding dsh-agent-team-gui: true under allowBuilds in ~/.dsh/profiles/web/pnpm-workspace.yaml, then restart the running DeepSeek Harness Web process after installation or updates.
Requirements and limits
DeepSeek Harness must be >=0.1.0-rc.5 <0.2.0, using the Web profile. The environment needs Node.js >=22.19.0 <23 or >=24.0.0; Node.js 23 is unsupported, and pnpm plus at least one configured DSH provider/model route are required. A compiled release tarball does not need Git prepare permission.
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-team-gui
dsh-plugin
Tabbit-Browser
Tabbit Broser plugins for Deepseek Harness
Installed cleanly when we ran it
dsh_workflow
icetomoyo
UltraCode-style multi-agent orchestration: a generatable, savable, governable, observable, resumable workflow layer.
Installed cleanly when we ran it
dsh-automation
titanwings
Scheduled coding runs in fresh agent sessions with auditable history.
Installed cleanly when we ran it
mstar-harness
btspoony
Skill-driven harness/loop engineering workflow agent plugin.
Installed cleanly when we ran it
agent_team_gui
toolclub
Reusable agent squads with per-agent provider/model routes and tool policies, serial/parallel dispatch, spawn/fork/chain context modes, and a Web management panel.
Installs, but needs a build approved first