dsh-agent-team-gui

dsh-agent-team-gui

English | 简体中文

Give DeepSeek Harness a reusable team: one Agent plans, another implements, and a third reviews.

Save the team once, choose a model for each member, and reuse it across projects and conversations. Follow the plan, member outputs, retries, and provider-reported Token usage in one Run Center. This is an unofficial community plugin for the DeepSeek Harness Web profile.

Watch the 80-second UI guide · Install v1.3.0 · Run your first team · Example recipe · Share a workflow

*Screenshot-based UI guide with example data and Chinese synthetic narration. Displayed task results, timings, and Tokens are not a live-run benchmark. Sources and captions.*

If this is useful for your DSH workflow, give the project a Star and help another developer discover it. Why this plugin

A team is a reusable product object, not a one-off dispatch form. Create it once in Settings → Teams, then use it across projects and conversations. Install | 1.3.0 | >=0.1.5-rc.1 =0.1.5-rc.1 =0.1.5-rc.1 =0.1.5-rc.1 =22.19.0 =24.0.0, and pnpm. Declared DSH compatibility is >=0.1.5-rc.1 [!TIP] If dsh is not on PATH, use the launcher that starts your working Harness installation. With npm, replace dsh with npx @deepseek-ai/dsh@0.1.5-rc.1; from a source checkout, replace it with pnpm --dir /absolute/path/to/deepseek-harness dsh. Keep the same launcher for installation and startup. New to Harness? Start with its official setup guide.

Verify that both the dsh-agent-team-gui bundle and the agent-team-gui configuration row are present:

Run your first team

Use the included full-stack delivery recipe, with a planner, implementation engineer, and reviewer. You can bind all three to the same working model for the first run; multiple providers are optional.

1. Download the recipe JSON. Open Settings → Teams → Recipes & data and choose Choose recipe file. 2. Map the placeholder routes to your configured provider/model routes, review the preview, and choose Create a copy → Import reviewed recipe. In Member library, confirm each member's exact model and tool access. 3. For this first walkthrough, set Team usage → Host dispatches first, Dispatch policy → Run assigned work, and member selection to All members, then save. The supplied recipe otherwise uses Smart/adaptive selection. 4. Select an empty scratch project, choose the imported team beside the composer, select Select team for this conversation, and send the ready-to-copy task: build and test a small to-do list. 5. Open Team runs to inspect the plan, outputs, review, and actual Token coverage. Check the delivered files and test results before treating the task as complete.