{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "toolclub-dsh-agent-team-gui--reuse-team-across-projects",
 "repo": "toolclub/dsh-agent-team-gui",
 "repo_url": "https://github.com/toolclub/dsh-agent-team-gui",
 "repo_slug": "toolclub-dsh-agent-team-gui",
 "title": "Save a team once and reuse it across projects",
 "page_title": "How to save a team once and reuse it across projects with DSH Agent Team Gui",
 "summary": "Define a planner, implementer, and reviewer with their own models, then select the team per conversation or per project.",
 "who": "A developer who repeats the same multi-step workflow across several repos and wants one saved team instead of a new dispatch each time.",
 "problem": "Re-creating the same agent roles and model choices for every project costs time and produces inconsistent results.",
 "outcome": "A named team in Settings → Teams that you can attach to any project or conversation with the Team, Solo, or Inherited modes.",
 "steps": [
  "In Settings → Teams → Member library, save each member's role, model, optional fallback, and tool policy.",
  "In Settings → Teams, add those members and choose activation, member selection, and execution options.",
  "Leave Fixed order off for dynamic planning, or enable it if you need a fixed serial sequence.",
  "Choose Team, Solo, or Inherited beside the composer to control the current conversation.",
  "Run a short test task in one project, then reuse the same team in a second project to confirm the selection holds."
 ],
 "agent_prompt": "Using the dsh-agent-team-gui repo, create a team named <team-name> in Settings → Teams with a planner, an implementer, and a reviewer, each with its own model route. Report the saved member list and the activation settings. Verify that the team still appears after a page refresh.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "Team members use the model routes you assign in DSH, so a team only works in projects where those routes are configured.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "A working DeepSeek Harness installation with the Web profile, at or above the DSH compatibility version listed in the README install table (>=0.1.5-rc.1)",
  "Node.js and pnpm at the versions listed in the README install table",
  "The dsh-agent-team-gui plugin installed from the README install section",
  "At least one provider/model route configured in DSH"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/toolclub-dsh-agent-team-gui/reuse-team-across-projects/",
 "md": "https://dedupedai.com/use-cases/toolclub-dsh-agent-team-gui/reuse-team-across-projects/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/toolclub-dsh-agent-team-gui--reuse-team-across-projects.json",
 "api_version": "v1"
}