whyihaveyou/dsh-suite#plugin-team-board
Shared multi-agent task board (create/claim/transition/query) over a Cordis service key.
plugin-team-board provides a shared task board for multi-agent / subagent collaboration in DeepSeek Harness: create, claim, update and list tasks across subagents, persisted through the append-only session log. It is one of the first-party plugins maintained in the dsh-suite monorepo, in the Workflow & Automation category.
Install
dsh plugin --profile web add @dsh-suite/plugin-team-boardPackage listed in the dsh-suite monorepo catalog (README). The install uses the same DSH form the README Quick Start shows for this monorepo's sibling package @dsh-suite/plugin-manager ('dsh plugin --profile web add @dsh-suite/plugin-manager'), with the package name swapped. The npm package @dsh-suite/plugin-team-board 0.2.1 was re-verified live on 2026-10-02 with its repository field back-linking to whyihaveyou/dsh-suite. IMPORTANT: the author's own daily compat CI flags @dsh-suite/plugin-team-board@0.2.1 as incompatible with dsh 0.2.0-rc.2 (peerDependencies), with the same allow-version escape hatch documented for its siblings.
Compatibility
DSH Web UI, part of the whyihaveyou/dsh-suite monorepo. Task state is persisted via the append-only session log. Compatibility caveat: the author's CI install check against dsh 0.2.0-rc.2 fails with a peerDependencies mismatch, so a plain install may be rejected on that harness version.
Details
- Repo: whyihaveyou/dsh-suite#plugin-team-board
- Category: Workflow & Automation
- Stars: 0
- Version: npm @dsh-suite/plugin-team-board 0.2.1 (registry re-verified 2026-10-02)
- Last push: 2026-09-21
- First seen: 2026-08-13
Recent updates
The README documents the dsh-suite catalog entry for @dsh-suite/plugin-team-board (shared multi-agent task board) and its compatibility status in the same catalog table (flagged broken against dsh 0.2.0-rc.2 by daily CI).
FAQ
- How do I install plugin-team-board?
- dsh plugin --profile web add @dsh-suite/plugin-team-board (npm 0.2.1 re-verified 2026-10-02); the author's CI flags a peerDependencies mismatch with dsh 0.2.0-rc.2.
- What is it for?
- A shared task board for multi-agent / subagent sessions: create, claim, update and list tasks across subagents, per the catalog entry.
- Where is the task state stored?
- The catalog entry says tasks are persisted via the append-only session log.
Alternatives
whyihaveyou/dsh-suite#plugin-manager · whyihaveyou/dsh-suite#plugin-notify · whyihaveyou/dsh-suite#plugin-session-export