whyihaveyou/dsh-suite#plugin-team-board
Shared multi-agent task board (create/claim/transition/query) over a Cordis service key.
Install
This plugin lives in a subdirectory of a larger repository, and `dsh plugin add` cannot reach it — it forwards to pnpm, which reads everything after `#` as a git branch or commit. Clone the repository and add the plugin through DSH's plugin panel using a repository source, or ask the author to publish it to npm.
Due diligence
What it is — plugin-team-board provides a shared multi-agent task board that supports subagents to create, claim, transition, and query tasks over a Cordis service key, based on append-only session log persistence.
Who it is for — When using multiple subagents in DeepSeek Harness to collaboratively handle complex tasks, plugin-team-board is suitable as a shared task platform. Users who rely on a single agent or do not need cross-agent task sharing should skip it.
Watch out — Requires an API key or token. Installed as a subdirectory plugin with no one-click command. Executes shell commands. No obvious issues found.
The verdict — If coordinating task state across subagents in DeepSeek Harness, it is worth installing because it persists append-only session logs; the premise is access to a Cordis service key.
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.
plugin-team-board is a DeepSeek Harness plugin that provides a shared task board for multiple agents. It supports creating, claiming, transitioning and querying tasks across agent sessions through a Cordis service key.
The board is accessed through that service key rather than being limited to one agent session. The directory description also states that task data is persisted in an append-only session log. This gives agents a shared record of task state and ownership, while retaining a log of changes rather than treating the board as an in-memory view. The documented operations are:
DeepSeek Harness users may consider plugin-team-board when several agents need to coordinate work through a common task state. It is a poor fit for a single-agent workflow that does not need shared task tracking, or for an environment where supplying the required credentials and Cordis service key is not acceptable. The source does not document the command syntax, configuration keys, or supported platforms, so those details should be checked before deployment.
The listed risk flags indicate that plugin-team-board reaches a terminal surface and requires credentials. The terminal access is part of the plugin’s execution boundary; the credentials are needed for access through the Cordis service key. Install it only in a profile whose agent permissions and credential scope are suitable for shared task operations.
The directory describes plugin-team-board as a multi-agent task board whose state is persisted through an append-only session log. This provides a recorded sequence of task-related changes rather than an undocumented in-memory state. The upstream summary additionally identifies a Cordis service key as the access mechanism.
The available documentation does not define the log file path, record schema, retention behaviour, or whether logs can be edited or removed. Treat the session log as part of the plugin’s data surface when reviewing a profile for deployment.
plugin-team-board exposes four documented task operations:
create — create a taskclaim — claim a task for an agenttransition — move a task through its workflowquery — query tasksThese names describe the supported actions, not a documented command-line syntax. The source does not specify argument names, task fields, transition values, output formats, or the interface through which DeepSeek Harness invokes them.
A Cordis service key is required, and the repository metadata marks the plugin as requiring credentials. The metadata also marks a terminal surface, so the plugin should be assessed within the permissions of the profile in which it runs. No credential variable, configuration key, default value, platform restriction, or version requirement is documented in the supplied source.
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
Q00
Config-only bundle that mounts Ouroboros through the DSH MCP client, exposing 36 interview, Seed, execution, evaluation, and evolution workflow tools in DSH.
No one-line install — this plugin lives inside a larger repository and publishes no npm package.
loopx-project
LoopX, a provider-neutral, local-first state kernel and control plane for long-horizon agents: keeps Goal, Todo, gate, evidence, quota, recovery, and handoff state above DeepSeek Harness, while the plugin bootstraps the CLI and skills, admits bounded same-session continuation, and adds a loopback GoalBar for the exact bound loop.
No one-line install — this plugin lives inside a larger repository and publishes no npm package.
huangruiteng
LoopX, a provider-neutral, local-first state kernel and control plane for long-horizon agents: keeps Goal, Todo, gate, evidence, quota, recovery, and handoff state above DeepSeek Harness, while the plugin bootstraps the CLI and skills, admits bounded same-session continuation, and adds a loopback GoalBar for the exact bound loop.
No one-line install — this plugin lives inside a larger repository and publishes no npm package.
chuspeeism
Embeds the active installed Codex Taskboard runtime in the DeepSeek Harness sidebar, using its launcher runtime descriptor instead of a fixed port.
No one-line install — this plugin lives inside a larger repository and publishes no npm package.
tong-io
TongFlow film-crew studio for image, voice, music and video production: the agent writes per-asset TongFlow workflow files (.tongflow.json) that run through TongFlow plugins, with an embedded workflow canvas, a shot/character/take project layout and a manga-drama template; sessions starting with @tongflow open the Studio view.
No one-line install — this plugin lives inside a larger repository and publishes no npm package.