dsh-team-rooms

dsh plugin --profile web add dsh-team-rooms

Retired (2026-10-05): DeepSeek Harness now ships the native Agent Teams subsystem. This package remains installable for reference; use the native Agent Teams for new work.

Native: https://github.com/deepseek-ai/deepseek-harness · Source: https://github.com/PerryLink/dsh-team-rooms

<div align="center">

🏠 dsh-team-rooms

• 1024 store channel: npm i -g dsh1024 once, then dsh1024 plugin --profile web add dsh-team-rooms (counts toward the deepseek1024.com install ranking).

Persistent, cross-session multi-agent team rooms for DeepSeek Harness — members, a message bus, a shared task board, and a shared timeline that survive restarts.

Each member is an independent DSH session; the room is the shared durable object between them.













[English](README.md) · [简体中文](README-zh.md) · [Español](README-es.md) · [Português](README-pt.md) · [हिन्दी](README-hi.md)

</div>

---

Extracted from dsh-background-agents 0.9.6. The background-agent half of that plugin (background_agent and the five bg_ tools) is superseded by DSH's native continuable subagents; the team-room half had no native equivalent and lives on here as its own package. Storage domains, session logs, and settings written by 0.9.6 keep working unchanged — see Compatibility*.

Compatibility

Host 0.1.2-alpha.2 and later fails closed on the session event vocabulary, so this plugin no longer writes its log-only fact events (team-room/fact) there: facts route to the logger/panel channel instead and the teamRoom projection degrades to an empty fold. Older rc lines (through 0.1.1-rc.2) keep the ignorable-marker discipline. The client half rides the current client packages (dsh-api-session-controller, dsh-client-ui-slots, dsh-client-ui-settings, dsh-client-locale, dsh-client-web).

Data compatibility with dsh-background-agents 0.9.6 is a hard rule. These strings are byte-identical to 0.9.6 and must never be renamed: the storage domain team_rooms, the teamRoom projection key, the team-room/fact session event type, and the team-rooms settings-slot id. An existing profile therefore keeps its rooms, its member logs, and its settings page when you swap the plugin.

Surface · Status

Harness · DeepSeek Harness dsh-v0.2.1-alpha.1 (verified 2026-09-25; dev and runtime pins 0.1.7-rc.2, peers >=0.1.2-rc.1 <0.2.0 \ · \ · >=0.1.5-alpha.1 <0.2.0 \ · \ · >=0.1.6-0 <0.2.0 \ · \ · >=0.1.7-0 <0.2.0)

Node · ^22.19.0 \ · \ · >=24.0.0

Platforms · All (host tools; the settings page needs the Web client half and the storage-domain capability)

Model · Any (rooms carry no model route — members are ordinary sessions)

What you get

dsh-team-rooms turns several independent sessions into one coordinated team:

1. The /room command family — create, join, leave, list, send, tasks, task add|assign|claim|done|delete. Rooms are named, owned, and addressed by a stable room id you can paste into another session.

2. **Eight room_* tools** — room_list_rooms, room_post, room_read, room_list_tasks, room_create_task, room_claim_task, room_transfer_task, room_complete_task. The model works the shared board and the bus from inside its own session; room_transfer_task asks for approval before a cross-member handoff.

3. A durable room store — members, the message bus (directed or broadcast), the task board, and the timeline live in the team_rooms storage domain (SQLite or JSONL backend — the deployment chooses; the plugin adds no service of its own) and recover across DSH restarts.

4. A Web settings page — the Team Rooms settings section shows member status, the task board, and the timeline of every room the current session belongs to, read from the teamRoom session projection and written back through the host /room command.

Quick start

# 1. install the bundle into your profile
dsh plugin --profile web add "github:PerryLink/dsh-team-rooms#main"

# or from npm (published releases)
dsh plugin --profile web add dsh-team-rooms

# 2. restart and verify the row
dsh --profile web --dump-config | grep -A4 'id: team-rooms'

The bundle patch carries the plugin row; no Config key is required. The repo commits its build output (lib/), so git installs need no build step. Rooms mount wherever the stora

…(truncated)