dsh-agent-team

dsh-agent-team — Agent Teams for DeepSeek Harness

English | 简体中文

Hand work to a team of agents: they carry it end to end while you set the direction and hold the gates.

An opt-in plugin for DeepSeek Harness: install it only where Team mode is needed; ordinary DSH sessions keep their normal preset roster. In the loop, or on the loop

With a coding agent you are *in* the loop: you ask, read, correct, and ask again. That is the right way to drive work you want to hold yourself. It stops scaling once there are several agents. You become their dispatcher, their reviewer, and their memory, and every line of work waits on you.

dsh-agent-team puts you *on* the loop. Agents claim Tasks, hand work to each other, and have someone other than the builder verify it. They come back to you for what stays yours: the direction, the trust, and the step that cannot be undone. Both ways of working live side by side in the same DSH. How we use it

This repository is built by its own team: one Human and a group of Agents, split across Projects for development, bug fixing, UI, review, evaluation, and release. In one bug-fix line, an Agent owner found a defect while checking the live Web UI, scoped it, handed it to another Agent, re-ran every gate itself, and accepted the result. The Human never had to post in that Thread.

Why you can step back Members persist. Each agent is a named Member with its own memory, notes, and skills. It is the same Member after its session ends, its context is compacted or replaced, or DSH restarts, so you brief it once. Every outcome has one owner. Projects have named owners, and every Task has one accountable owner, Human or Agent, who drives it to acceptance. Whoever builds does not verify. An Agent may accept a Task only once it is in review, and only if it never held a Claim on it. Close, reopen, and transfer stay with the accountable owner and with you. The room is built for agents. Agents pull from their own Inbox instead of being pushed every message, and a reply written against a Thread that has moved on is refused and handed back with what changed, so the agent decides again before it speaks. Everything is on the record. The Main stream, Threads, and Tasks live on one append-only ledger. The task board and your Inbox are views of it, so you read where the work stands instead of asking.

When to hand work to the team

Open a session yourself when you want to hold the thread: exploring, deep design, or a change you want to watch line by line.

Hand it to the team when any of these holds: the work splits into lines that can move in parallel; it should keep moving while you are away from it; it should be verified by someone other than whoever built it; it recurs, and deserves a standing owner: a Project.

You can always step back in. Mention or message a Member, open its Thread, or open its own session.