dsh-agent-teams-meta

Bug triage, change review, multi-angle comparison of approaches—these tasks are naturally parallelizable, yet a single agent can only work through them sequentially. dsh-agent-teams-meta turns a DSH lead agent into a team builder: it composes durable members, each with its own role, provider/model route, and private mailbox, while the lead delegates work, tracks dependencies, and collects results—all inside a real DSH session rather than a simulated chat room.

Members can run on entirely different provider/model pairs within the same team. Tasks carry an owner and prerequisite dependencies, so a member can only claim work whose prerequisites are already satisfied. The lead can switch a member to another configured route at any time; the next outbound request picks up the new route while an in-flight one keeps its original attribution. Every participant sees only its own mailbox, keeping the signal-to-noise ratio high. On creation the plugin validates routes against a workspace-local catalog of currently configured models, rejects unknown providers up front, and logs per-request token usage against the active route for clean auditing. A read-only drawer in the DSH Web sidebar surfaces team phase, member status, and task progress without altering the source of truth.

Developers who work in DSH and need to parallelize multi-step workflows will find it useful: assigning different sub-tasks to different models for cost or quality reasons, accelerating work without losing intermediate state, or simply wanting a structured collaboration mechanism with persistent mailboxes and task dependencies instead of juggling multiple chat windows and manually stitching contexts together.