Skip to main content

dsh-agent-team-gui

111Stars1Forks0Issues0Watchers

Inject a reusable multi-model agent team into DeepSeek Harness Web: team members independently configure models and tools, collaborate via dependency graph, with persistent runtime history and official token usage tracking.

Evidence5/5methodologySourceInstallMaintenanceDSH versionSecurity scan
Machine-auditedInstall commandRepo verifieddsh-plugin topicLicenseREADMEAI wiki
Language
TypeScript
License
MIT
Branch
main
agentagent-orchestrationai-agentsdagdeepseek-harnessdeepseek-harness-plugindshdsh-plugin

Install

cmdweb profile
$ dsh plugin --profile web add --allow-build=dsh-agent-team-gui github:toolclub/dsh-agent-team-gui

Run the command above in your terminal to install this plugin via the dsh CLI. You can switch Profile in the top-right corner. New to dsh? Read the beginner tutorial

Install via your agent

Install the DeepSeek Harness plugin toolclub/dsh-agent-team-gui for me: review the repository at https://github.com/toolclub/dsh-agent-team-gui first, then run the install command and verify the plugin loads successfully.

Paste this instruction to the DSH Web GUI assistant — it will install and verify for you.

One-Line Positioning

Inject reusable, version-controllable multi-model Agent squads into DeepSeek Harness Web, allowing users to select persistent "teams" alongside the regular chat dialog, with the main model automatically dispatching, aggregating, and recording official Token usage based on a bounded dependency graph.

Core Capabilities

  • Create reusable member pools in Settings: each member independently binds provider/model, dedicated role prompt, optional fallback route, Token cap, and minimal permission tool whitelist
  • Create persistent squads in Settings: combine members, choose serial or parallel, set activation strategy (always/intelligent/manual) with optional quality gates
  • Switch between Team / Solo / Inherited three modes beside the regular chat dialog, stackable with one-time "next message" selection and project-level defaults
  • Dynamic DAG orchestration: current conversation's model acts as bounded planner to generate role assignments and acyclic dependency graph, automatically falling back to deterministic role assignment on failure
  • Background run, cancellable, retryable, writes to persistent run history, main model only sees bounded handoff information
  • Directly display official provider-reported Token usage (input/cache read/cache write/output) with full/partial/no coverage, never fake pricing

Technical Implementation

  • Language: TypeScript (Host service + React 18 Web client, dual tsconfig separate builds)
  • Key Dependencies: @deepseek-ai/cordis (Cordis dependency injection container), @deepseek-ai/dsh-agent/dsh-llm/dsh-storage/dsh-storage-domain/dsh-tools/dsh-jobs (host service seams), zod (all read/write schemas), @deepseek-ai/schemastery (config schema), react@^18.2.0 (Web UI)
  • Architecture Pattern: Dual-end Cordis services — Host side injects via Service class into DSH host process, intercepts regular messages in agent/pre-step hook and dispatches according to squad mode; browser side injects into 4 existing additive slots (settings.section, conversation.input.right, conversation.input.dock, conversation.view), and communicates with Host via loopback-only Connection RPC (/agent-team-gui); Domain uses 8 tables (agents/squads/session_modes/next_modes/message_claims/runs/squad_versions/project_defaults) for v0 persistence, strictly separating new write schemas from loose v0 read schemas
  • Entry Files: Host side src/index.ts; browser side src/client/index.ts; model tool src/tools/dispatch-to-squad.ts; RPC adaptation layer src/rpc.ts; Domain specification src/spec.ts; Cordis injection declarations cordis.patch.yml

Use Cases

Suitable for DSH users doing "long-task multi-role collaboration" in Web profile — for example, having a squad simultaneously take on planning, implementation, review, and repair roles, automatically dispatching by dependency; also suitable for team administrators who need to reuse team configurations (model routing, role assignment, trigger strategy) across projects. If you only want a single conversational agent, or don't enable Web profile at all, this plugin is not appropriate.

Prerequisites and Compatibility

DependencyMinimum VersionNotes
DeepSeek Harness>=0.1.0-rc.5,<0.2.0peerDependencies declaration range; CI currently validates 0.1.0-rc.6
Node.js^22.19.0 or >=24.0.0engines field; README explicitly states "Node 23 not supported"
DSH profileWeb profile onlyrepo dsh.bundle.client.platform=web, only registers UI for Web bundle
DSH provider/modelAt least oneSquad members need to bind existing DSH routes, credentials managed by DSH
pnpmAny supported versionpnpm 10+ may require allowBuilds for Git source installation

Installation

dsh plugin --profile web add github:toolclub/dsh-agent-team-gui

Configuration Options

ConfigTypeDescriptionDefault
defaultProviderstringDSH sub-Agent default provider name, used as fallback when creating membersspawn
defaultExecutionModeserial / parallelFallback execution mode when squad doesn't specify (serial or parallel)serial
defaultContextModespawn / fork / chainFallback context mode when squad doesn't specify; chain only valid under serialspawn
historyMaxRuns0~5000 integerAuto-cleanup how many finished runs; 0 means no quantity-based cleanup0
historyMaxAgeDays0~3650 integerAuto-cleanup finished runs older than how many days; 0 means no time-based cleanup0
versionMaxPerSquad0~1000 integerMaximum immutable versions to keep per squad; 0 means no version cleanup0

FAQ

Q: Do I need to restart DSH Web process after installation?

A: Yes. README explicitly requires restarting Web process after installation or update, so new agent-team-gui Host entry gets loaded.

Q: Must I use Web profile? Can headless install it?

A: Web is required. Settings UI, conversation mode controls, and Run Center all depend on Web bundle's injected storage and Connection RPC; other in-process plugins can call exported Host services if they inject required services, but there's no official config UI.

Q: What else do I need to prepare before installation?

A: DSH between 0.1.0-rc.5 and 0.2.0, Node.js 22.19+ or 24+ (Node 23 not supported), pnpm, and at least one provider/model route already configured in DSH — squad members must attach to existing routes.

Q: Does uninstalling the plugin also delete squad data?

A: No. Plugin removal doesn't automatically delete the 8 persistent domain tables, squad definitions, versions, and run history remain in DSH storage; manual cleanup required.

Q: What to do when pnpm shows allowBuilds prompt during installation?

A: Only add dsh-agent-team-gui to the Web profile workspace file's (default ~/.dsh/profiles/web/pnpm-workspace.yaml) allowBuilds, authorize no other packages, then repeat the same fixed-version command.

Q: Can old v0.4 data still be used?

A: Can be opened and imported, but can no longer write with v2 caps. Old runs without original plan recorded will be explicitly rejected for retry.

Q: Does model tool invocation always trigger the squad?

A: Not necessarily. Model tool triggering is best-effort because DSH hasn't exposed toolChoice control; for stable auto-triggering, set squad trigger mode to guaranteed, which is Host-driven and idempotent via persistent messages.

Q: Can I fetch recipes from remote URLs?

A: No. snapshotSchema.capabilities.remoteRecipeFetch is fixed to false, v0.5 intentionally disables remote URLs to avoid exposing Host network surface without SSRF hardening; please import locally-reviewed JSON instead.

Learning Curve

Advanced — requires first understanding DSH Web profile and Cordis injection model, then reading the "member-squad-trigger mode" config matrix in Settings; additionally, quality gates, activation strategies, and context modes (spawn/fork/chain) significantly affect squad behavior, so just reading README without running through it can easily lead to pitfalls.

Known Issues and Limitations

  • Web profile only; no headless Settings page; other in-process plugins can consume exported Host services, but official config UI doesn't exist (README.md:334-335)
  • Declared compatibility range >=0.1.0-rc.5 <0.2.0, but CI only validates on rc.6, neither DSH nor this plugin is stable, production must pin versions (README.md:336-337)
  • Model tool trigger mode (model-tool) is best-effort: DSH doesn't expose toolChoice control, model may not automatically call dispatch_to_squad; use guaranteed mode for stable auto-triggering (README.md:346-347)
  • DSH currently has no official seam for "registering custom squad/* Session events", plugin implements via own persistent run table + standard child Session/Tool events + Jobs + logs combination, event visibility inconsistent with official Session events (README.md:344-345)
  • Soft Token budget (tokenBudget) can only prevent subsequent members from being scheduled, cannot forcibly interrupt already-running provider; true hard cap is each member's own maxTokens (README.md:342-343)
  • v0.5 bans recipe fetching from URLs: snapshotSchema.capabilities.remoteRecipeFetch hardcoded to false, README explicitly states it's to avoid exposing Host network surface without SSRF protection (src/rpc.ts:259-261 / README.md:192-193)
  • Provider Token projection is optional capability, partial/unavailable coverage is normal and explicit state; UI shows "Metering..." before receiving any reports, no fake 0 (README.md:154-165)
  • v0 persistence definition domain version: 0 intentionally preserved and storage-domain provides no migration API, Domain table structure only adds not deletes (src/spec.ts:347-352)
  • No TODO/FIXME/HACK/XXX comments found in source code (grep result empty), no developer-marked todos

Read the usage guide →

Install steps, key points, FAQ and compatibility for this plugin — auto-derived from indexed fields.

Listing badge

Listed on deepseek-plugin.org
[![Listed on deepseek-plugin.org](https://img.shields.io/badge/listed_on-deepseek--plugin.org-007EC6)](https://deepseek-plugin.org/plugins/toolclub/dsh-agent-team-gui)

Paste this markdown into your GitHub README to link back to this listing. The badge only states the listing — not a security endorsement.

← Back to plugin directory