Introduction

In the plugin extension scenarios of DSH, sub-agents are frequently used to distribute tasks. However, when multiple agents run simultaneously without names, memory, task lists, and message channels, the operational state easily degenerates into a tangled mess of untraceable session streams.

dsh-team addresses this issue: It launches a visible team of agents within DeepSeek Harness, assigning identities to each teammate, and ensuring that tasks, messages, workspaces, and collaboration rooms are traceable within the session.

What is this

huxint/dsh-team is a DeepSeek Harness (DSH) plugin maintained by huxint, licensed under the MIT License.

Its one-sentence positioning is: add a visible team of agents to DeepSeek Harness.

It solves the core problem of: when a task requires collaboration among multiple agents, how to ensure teammates have names, roles, and memory, can communicate with each other, claim shared tasks, write to shared workspaces, and view real-time status in the ‘Agent Team’ tab.

Core Capabilities

The following introduces the confirmed capabilities of dsh-team.

  • Permanent Teammates: Each teammate has a name, role, and their own memory. They are always available and do not require repeated background context.
  • Member Communication: Teammates can communicate directly with each other without needing to route everything through you.
  • Shared Task List: The entire team claims the same list, making it clear who is responsible for which task.
  • Shared Workspace: A blackboard shared by the entire team, plus a private notepad for each member that others cannot see; content written remains after a restart.
  • Collaboration Room Tab: An office that updates in real-time, giving you a comprehensive view of everything the team is doing.
  • Safety Boundaries: Conversations between teammates are limited in number of turns, preventing endless loops; messages sent to the main session are always accessible.

Installation and Activation

First, install the plugin. The official installation command is as follows:

dsh plugin --profile web add dsh-team

It takes effect immediately after installation.

Note: The plugin runs with the permissions of the current DSH process. It is recommended to review the source code and license before installation.

Typical Usage

  1. Type in the DSH input box:
/agent-teams 把鉴权模块迁移到新 SDK

The content after the slash is the goal for the team and can include images.

  1. You can also avoid typing a command and simply say “form a team to do this” directly in the main session. It will determine how many teammates are needed and what roles they should play.

  2. Teammates claim and work on tasks, and progress is automatically reported back to your session.

  3. To view the on-site situation, click on the ‘Agent Team’ tab to enter the collaboration room.

  4. To have a specific teammate finish their work or to disband the entire team, simply mention it to the main session.

Suitable Scenarios and Notes

Who is it for:

  • You want to split a task and have multiple agents collaborate to complete it;
  • You want to see task assignments, progress, messages, and workspace status directly within the session;
  • You want simple collaboration channels between teammates but do not want the conversation to get out of control;
  • You want to be able to review relevant historical records in the harness’s sub-agent panel even after the team is disbanded.

Usage Notes:

  • What teammates communicate with each other about is only known to the involved members; what you see is traffic related to you.
  • The shared task list is managed by the main session; teammates deliver results by reporting them.
  • The shared blackboard in the collaboration room displays a snapshot taken when the main session last performed a read or write operation.
  • After the entire team is disbanded, each teammate’s history can still be browsed in the harness’s sub-agent panel—this is by design.
  • When the main session is offline, newly added teammates temporarily cannot access team tools until the main session returns.
  • Teammates cannot create their own teams.
  • Configuration options are written in cordis.patch.yml for overrides; these options all have default values and can be used directly without any configuration.

Conclusion

The value of dsh-team is to organize multiple agents within DSH into a team that has names, memory, task lists, shared workspaces, and collaboration rooms. It does not emphasize exposing every single detail to you, but rather allows you to see progress relevant to you and enter the scene when necessary.

  • GitHub: https://github.com/huxint/dsh-team
  • Directory Page: No verified link provided at the moment; please refer to the actual site for the link.