dsh-team-progress

dsh-team-progress

A DeepSeek Harness GUI plugin showing four views of a running agent team, counted from

durable state: who is on what, which defects are tracked, how far the goal has moved,

and what needs a human now. A source it cannot read renders unavailable with the

reason instead of a 0.

The host half (lib/index.js) registers one loopback JSON route

POST /api/team-progress/rpc on the webServer service; the client half

(lib/client.js) registers the panel with the slot service and re-reads that route

every 5 seconds while the panel is open.

The panel

STALLED  task task-5   owner beta is inactive        ← 4. act now, FIRST
BLOCKED  task task-6   waiting on task-4

3/6 tasks · 2/3 members                               ← headline
▓▓▓▓▓▓▓░░░▓

MEMBERS   4                                          ← 1. who is on what
  member   status    claimed task    task status
  lead     running   task task-6     pending
  alpha    running   task task-4     in progress
  beta     inactive  task task-5     in progress   STALLED
  gamma    running   no claimed task

DEFECTS   10 fixed · 5 in flight · 4 open (19)       ← 2. tracked defects
  #2   Repo→app mapping is dead code.
  #17  False CRITICAL.
  +2 more open

GOAL      round 7/256 · active · armed               ← 3. goal progress
  Extend dsh-team-progress with the four views

conversation.view   id "team-progress", order 30   a "Team progress" session tab
POST /api/team-progress/rpc   { method: "state" }  the payload

The panel is one conversation.view tab, bound to the session it was opened in. The

registration at mount() in lib/client.js is the authority on what is rendered: it

registers that tab and nothing else.

What it adds

• MEMBERS — one row per member: live status, the shared task it claims, that

task's status. A member holding nothing renders no claimed task.

• DEFECTS — counts by status across the configured defect logs, plus the rows

still open. Recognised: open / in flight / fixed / closed as superseded;

anything else is counted as other and displayed as unclassified.

• GOAL — rounds begun against the cap, the phase, and armed / disarmed.
• STALLED / BLOCKED — the action list, rendered first because a stall is the only

state that asks for a decision.

• One RPC route — POST /api/team-progress/rpc, methods state and act.
• One optional action surface — complete / reopen / claim / release / reassign, wake,

interrupt, spawn, auto-assign, broadcast, member cap, all through the same domain

methods the model's own tools call. Off by default; see [Security](#security-the-action-surface).

Requirements

The read path was traced against DeepSeek Harness 0.2.1-rc.3 (2026-10-24), and the

plugin was last exercised end to end on 0.2.1-rc.5 (2026-11-03): a

POST /api/team-progress/rpc with {"method":"state"} answered 200 with a live

payload. No minimum version is declared.

• The client half is declared for the web platform (dsh.client.platform). It is

browser-plane code, so importing dsh-team-progress/client in Node fails with

window is not defined — that is the plane, not a defect.

• Only webServer is a hard injection. agents, agentTeams, sessionProjections,

goals, sessionQuery and uiWorkspace are resolved lazily, so a profile with one