Skip to content
Back to search

dsh-agent-team

dsh-agent-team gives DeepSeek Harness agents that don't reset: durable Members with their own memory, notes, and skills across sessions, rollovers, and restarts. You set the direction; agents coordinate through Channels and Tasks.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/Contexera/dsh-agent-team with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/Contexera/dsh-agent-team'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/contexera--dsh-agent-team/badge.svg)](/listings/contexera--dsh-agent-team)

HTML

<a href="/listings/contexera--dsh-agent-team"><img src="/api/listings/contexera--dsh-agent-team/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Check DSH

This release is certified against DSH `0.2.1-rc.2`. Install the DSH version explicitly rather than following `latest`: an unpinned install can resolve to a line outside the range this bundle declares. On DSH `0.1.7-rc.2`, stay on `@wowyuarm/dsh-agent-team` `0.1.15`. On DSH `0.2.0-rc.2`, stay on `@contexera/dsh-agent-team` `0.2.3`. On DSH `0.2.0-rc.1`, stay on `@wowyuarm/dsh-agent-team` `0.2.0`.

npx @deepseek-ai/dsh@0.2.1-rc.2 web

Install it globally if you want the `dsh` command for the steps below: `npm i -g @deepseek-ai/dsh@0.2.1-rc.2`.

Stop it, then install Agent Team into the `web` profile:

dsh plugin --profile web add @contexera/dsh-agent-team@0.2.4

The version is pinned deliberately: pnpm skips releases published less than 24 hours ago, so an unpinned `@latest` install resolves to the previous release on release day.

This plugin publishes as `@contexera/dsh-agent-team`, with its repository at `Contexera/dsh-agent-team`. The former `@wowyuarm/dsh-agent-team` stays at 0.2.1 and is deprecated in favour of the new name; an existing profile swaps the plugin's name, not its data.

2. Start the Web UI

dsh web

Do not start DSH from its source checkout (`pnpm dsh web`): source mode loads a second copy of the scope module, so every member reports `selected preset is not team-enabled`. Always start the compiled CLI.

Agent Team is opt-in. Installing it adds the bundle to the `web` profile; it does not modify the Harness installation or shipped defaults.

3. Verify and try it

Before starting the UI, you can inspect the composed profile:

dsh --profile web --dump-config

The output should include Team rows such as `wowyuarm-agent-team-scope` and `wowyuarm-agent-team-client`. In the browser, enter **Team mode** from the DSH navigation. The first useful path is:

Team mode
└── select a Workspace
    ├── Channels -> New Channel -> send the first message
    └── Agents   -> Add Agent -> choose its initial Channels

Create an Agent only in a trusted Workspace. The Team Member preset intentionally grants managed Agent Sessions `danger-full-access`.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 185 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # dsh-agent-team — Agent Teams for DeepSeek Harness
  2. [English](README.md) | [简体中文](README.zh.md)
  3. [![npm](https://img.shields.io/npm/v/@contexera/dsh-agent-team?style=flat-square)](https://www.npmjs.com/package/@contexera/dsh-agent-team)
  4. [![License](https://img.shields.io/badge/license-MIT-blue?style=flat-square)](LICENSE)
  5. [![Release](https://img.shields.io/github/v/release/Contexera/dsh-agent-team?include_prereleases&style=flat-square)](https://github.com/Contexera/dsh-agent-team/releases)
  6. [![Listed on Awesome DSH Plugin](https://awesome-dsh-plugin.com/badge.svg)](https://awesome-dsh-plugin.com/p/Contexera/dsh-agent-team/)
  7. **Hand work to a team of agents: they carry it end to end while you set the direction and hold the gates.**
  8. An opt-in plugin for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness): install it only where Team mode is needed; ordinary DSH sessions keep their normal preset roster.
  9. ## In the loop, or on the loop
  10. 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.
  11. 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.
  12. ## How we use it
  13. 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.
  14. ![A Main stream in the DSH Web UI: one Human message followed by five Task cards the Agent owner opened](assets/readme/one-sentence-five-tasks.png)
  15. ## Why you can step back
  16. - **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.
  17. - **Every outcome has one owner.** Projects have named owners, and every Task has one accountable owner, Human or Agent, who drives it to acceptance.
  18. - **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.
  19. - **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.
  20. - **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.
  21. ![A Project task board in the DSH Web UI: open Tasks owned by an Agent with their executors, and older finished Tasks still owned by the Human](assets/readme/task-board-owners.png)
  22. ## When to hand work to the team
  23. Open a session yourself when you want to hold the thread: exploring, deep design, or a change you want to watch line by line.
  24. Hand it to the team when any of these holds:
  25. - the work splits into lines that can move in parallel;
  26. - it should keep moving while you are away from it;
  27. - it should be verified by someone other than whoever built it;
  28. - it recurs, and deserves a standing owner: a Project.
  29. You can always step back in. Mention or message a Member, open its Thread, or open its own session.
  30. ![A Project Main stream in the DSH Web UI: the Human has unfollowed a Task and asks the Agent to report back when it is done](assets/readme/report-when-done.png)
  31. ![A Main stream in the DSH Web UI: the Human asks an Agent Project owner why it keeps asking for acceptance, and the owner answers where the line is](assets/readme/owner-sets-the-line.png)
  32. ## Where it stands today
  33. - **One machine.** One DSH server, one Human, and as many Agents as you create. Several Humans sharing one Team is not supported yet.
  34. - **Agents wake on Team events and on their own timers.** A message, a mention, a hand-off, or a reminder raised by activity wakes them; a Member's own reminder (one-shot, interval, or cron) and a Project subscription's polling interval also run on schedule. A Team with no active reminder or subscription and no event does not wake itself, and nothing runs while the machine is off.
  35. - **Agents work with full access.** Managed Agent Sessions run with `danger-full-access` in their Workspace, so create Agents only in a Workspace you trust.
  36. If this looks useful, a star on [GitHub](https://github.com/Contexera/dsh-agent-team) helps other DSH users find it.
  37. ## Quick start
  38. ### 1. Check DSH
  39. This release is certified against DSH `0.2.2-rc.2`. Install the DSH version explicitly rather than following `latest`: an unpinned install can resolve to a line outside the range this bundle declares. On DSH `0.1.7-rc.2`, stay on `@wowyuarm/dsh-agent-team` `0.1.15`. On DSH `0.2.0-rc.2`, stay on `@contexera/dsh-agent-team` `0.2.3`. On DSH `0.2.0-rc.1`, stay on `@wowyuarm/dsh-agent-team` `0.2.0`. On DSH `0.2.1-rc.x`, stay on `@contexera/dsh-agent-team` `0.2.6`. On DSH `0.2.2-rc.1`, stay on `@contexera/dsh-agent-team` `0.2.7`, which is also what npm `latest` resolves to while DSH's own `latest` is still `0.2.2-rc.1`.
  40. ```sh
  41. npx @deepseek-ai/dsh@0.2.2-rc.2 web
  42. ```
  43. Install it globally if you want the `dsh` command for the steps below: `npm i -g @deepseek-ai/dsh@0.2.2-rc.2`.
  44. Stop it, then install Agent Team into the `web` profile:
  45. ```sh
  46. dsh plugin --profile web add @contexera/dsh-agent-team@0.2.8
  47. ```
  48. The version is pinned deliberately: pnpm skips releases published less than 24 hours ago, so an unpinned `@latest` install resolves to the previous release on release day.
  49. This plugin publishes as `@contexera/dsh-agent-team`, with its repository at `Contexera/dsh-agent-team`. The former `@wowyuarm/dsh-agent-team` stays at 0.2.1 and is deprecated in favour of the new name; an existing profile swaps the plugin's name, not its data.
  50. ### 2. Start the Web UI
  51. ```sh
  52. dsh web
  53. ```
  54. Do not start DSH from its source checkout (`pnpm dsh web`): source mode loads a second copy of the scope module, so every member reports `selected preset is not team-enabled`. Always start the compiled CLI.
  55. Agent Team is opt-in. Installing it adds the bundle to the `web` profile; it does not modify the Harness installation or shipped defaults.
  56. ### 3. Verify and try it
  57. Before starting the UI, you can inspect the composed profile:
  58. ```sh
  59. dsh --profile web --dump-config
  60. ```
  61. The output should include Team rows such as `contexera-agent-team-scope` and `contexera-agent-team-client`. In the browser, enter **Team mode** from the DSH navigation. The first useful path is:
  62. ```text
  63. Team mode
  64. ├── Team manager -> shape the Team itself in a dedicated DSH conversation
  65. └── select a Workspace
  66. ├── Agents -> Add Agent
  67. └── Projects -> New Project -> choose its members -> post in its Main stream
  68. ```
  69. When an Agent should drive a Project's work, add it under **Owners** in **Edit Project**.
  70. Create an Agent only in a trusted Workspace. The Team Member preset intentionally grants managed Agent Sessions `danger-full-access`.
  71. ## Not to be confused with
  72. Three other DSH plugins carry similar names and solve a different problem — one of them may fit you better:
  73. | Plugin | What it is | Its unit of work |
  74. | --- | --- | --- |
  75. | [`NanmiCoder/dsh-agent-teams`](https://github.com/NanmiCoder/dsh-agent-teams) | Turns the current DSH session into a captain that assembles sub-agents, splits a goal into dependency-aware tasks, and coordinates them through direct messages | one **session** |
  76. | [`toolclub/dsh-agent-team-gui`](https://github.com/toolclub/dsh-agent-team-gui) | A reusable plan → implement → review team with a model chosen per member, and a Run Center for token usage | one **workflow run** |
  77. | [`limuyang2/agent-team`](https://github.com/limuyang2/agent-team) — publishes `@limuyang2/dsh-agent-team` | Builds a team of independent root agents inside one DSH window: mix models and providers, assign one Leader, and let every member work in its own conversation over a shared Workspace | one **assembled team** |
  78. | **`dsh-agent-team`** (this plugin) | Every agent is a durable, named Member with its own memory, notes and skills; Projects have owners, every Task has one accountable owner, and whoever builds a Task never verifies it | a **standing team** you lead from on the loop |
  79. The practical difference: in the other three, a team is assembled around the work at hand (a session, a workflow run, or a Leader-led team) and ends with it. Here the team stays. Its Members keep their memory, its owners keep their Projects, and work moves toward acceptance without waiting on you at every step.
  80. ## Uninstall
  81. Remove the bundle from the profile; this also removes its composed layers:
  82. ```sh
  83. dsh plugin --profile web remove @contexera/dsh-agent-team
  84. ```
  85. ## What it adds
  86. - A durable single-host Team: Workspaces, Projects with a Main stream and named owners, discussion and Task Threads, Claims, accountable owners, and a task board.
  87. - A Web Client for the Human: create Projects and Agents, set owners, post and reply, follow or step back from Threads, and accept, close, reopen, or transfer Tasks. The Inbox and a cross-Workspace task board show what needs you.
  88. - A dedicated Team manager conversation for shaping the Team itself. It is a Host-owned DSH Session, not a Member or ledger entity; it uses the shipped Conversation and composer, keeps private memory, and offers **New conversation** without changing Harness.
  89. - An isolated `team-member` preset with ten model-facing Team tools: `team_inbox`, `team_thread`, `team_attention`, `team_message`, `team_dm`, `team_task`, `team_view`, `team_subscription`, `team_reminder`, and `team_worker`.
  90. - A pull-based collaboration protocol. Agent Inbox admission is durable, but it does not claim that the model has already processed the update.
  91. ![Human Inbox in the DSH Web UI: one Thread needing you, with its unread and direct counts stated](assets/readme/inbox.png)
  92. The Team is one collaboration domain per DSH home. Its append-only operation ledger is the authority; UI, Remote responses, tools, Inbox, and other projections derive from committed operations. Ordinary DSH Sessions keep the profile's normal preset roster and do not receive Team tools or guidance.
  93. ## Install from a local checkout
  94. For development, install the local bundle into the same profile:
  95. ```sh
  96. dsh plugin --profile web add /absolute/path/to/dsh-agent-team
  97. dsh web
  98. ```
  99. Published packages include built artifacts. A local checkout needs the adjacent Harness repository only for development checks, not for end-user installation.
  100. ## Development
  101. Contributing: [`CONTRIBUTING.md`](CONTRIBUTING.md) — how to propose a change, what CI runs, and what a pull request should contain.
  102. Read [`docs/README.md`](docs/README.md) for the maintained documentation index. The usual checks are:
  103. ```sh
  104. corepack pnpm install
  105. npm run typecheck
  106. npm test
  107. npm run build
  108. npm run lint
  109. npm run test:browser
  110. npm pack --dry-run
  111. ```
  112. `npm run test:browser` uses the adjacent `../deepseek-harness` checkout, an isolated temporary profile, and `/usr/bin/google-chrome` (override with `CHROME_PATH`). It does not need provider credentials. For manual checks, `npm run preview:ui` loads Team fixtures without model streaming; `DEEPSEEK_API_KEY=... npm run preview` starts the real provider preview. Both preview commands clean up their temporary state on `Ctrl+C`.
  113. Architecture and the collaboration contract are documented in [`docs/architecture/README.md`](docs/architecture/README.md) and [`docs/team-collaboration/README.md`](docs/team-collaboration/README.md).
  114. ## Acknowledgments
  115. dsh-agent-team borrows a way of thinking from [Raft](https://raft.build/): an agent is a someone, not a something — a named teammate with its own memory and identity, working in a room shared with people. The concrete designs here differ in many places: Projects and their owners, Task Threads and their accountable owners, and the ledger underneath are this project's own. Thank you to the Raft team for the thinking.
  116. ## License
  117. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.