PerryLink/dsh-team-rooms
Team rooms for DeepSeek Harness: persistent shared rooms across independent sessions - a message bus, a shared task board and a timeline. Extracted from dsh-background-agents, whose background-agent half is superseded by DSH's native continuable subagents.
Project Overview项目介绍
dsh-team-rooms is a native DeepSeek Harness plugin authored by PerryLink that turns several independent DSH sessions into one persistent, cross-session multi-agent team. The package is distributed through the 1024 store channel: install the channel CLI once with npm i -g dsh1024, then add the plugin via dsh1024 plugin --profile web add dsh-team-rooms; alternatively, the bundle-manifest plugin is listed in the built-in DSH Desktop Market under the perrylink-dsh-catalog source, where installation still passes through npm-identity verification and a user confirmation step. The plugin registers itself under the storage slot team_rooms, exposes a dedicated settings page through dsh-client-ui-settings, slots into the Web client via dsh-client-ui-slots, and consumes dsh-api-session-controller plus the dsh-client-web, dsh-client-locale, and dsh-client-ui-settings client packages to mount its UI.
Each room is a named, owned, addressable durable object whose id can be pasted into another session: members are independent DSH sessions, the room itself is the shared object between them, and all room state — members, a directed or broadcast message bus, a task board, and a shared timeline — survives harness restarts. Users operate rooms through the /room command family (create, join, leave, list, send, tasks, plus the subcommands add, assign, claim, done, delete), while the model drives the same surface through eight room_* tools: room_list_rooms, room_post, room_read, room_list_tasks, room_create_task, room_claim_task, room_transfer_task, and room_complete_task; notably, room_transfer_task requires explicit approval before any cross-member handoff is committed.
Targeted at DeepSeek Harness 0.1.7-rc.2 with both dev and runtime pins locked to that build and peer ranges >=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, the plugin requires Node ^22.19.0 || >=24.0.0, runs on all host platforms supported by the Web client, and is model-agnostic because rooms carry no model route. It was carved out of dsh-background-agents 0.9.6 after DSH introduced native continuable subagents; the storage domain team_rooms, the teamRoom projection key, the team-room/fact session event, and the team-rooms settings slot must remain byte-identical for backwards compatibility, and on host 0.1.2-alpha.2 or later the stricter event vocabulary routes facts to the logger/panel channel instead of the session log. Licensed under Apache-2.0, it carries no runtime cost beyond the standard npm install.
dsh-team-rooms 是一个专为 DeepSeek Harness 设计的原生插件,由 PerryLink 维护,提供跨会话的多智能体团队房间功能。它通过 npm i -g dsh1024 安装 1024 store 通道后,使用 dsh1024 plugin --profile web add dsh-team-rooms 命令加载,或在 DSH Desktop Market 中添加 perrylink-dsh-catalog 源后再行安装。插件注册名为 team_rooms,遵循 bundle-manifest 规范,在 Web 客户端的设置页与 UI 槽位中提供独立的入口。
房间把若干独立 DSH 会话组织成一支持久团队,包含命名房间、成员列表、消息总线(支持点对点和广播)、共享任务板与时间线,所有内容在重启后仍可恢复。成员通过 /room create|join|leave|list|send|tasks|task add|assign|claim|done|delete 命令操作,或借助八个 room_* 工具(room_list_rooms、room_post、room_read、room_list_tasks、room_create_task、room_claim_task、room_transfer_task、room_complete_task)由模型自行驱动,其中 room_transfer_task 在跨成员交接前会请求用户审批。
要求主机为 DeepSeek Harness 0.1.7-rc.2,运行时锁定同版本,对等依赖范围 >=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,依赖 dsh-api-session-controller、dsh-client-ui-slots、dsh-client-ui-settings、dsh-client-locale、dsh-client-web。该插件从 dsh-background-agents 0.9.6 拆分而来,存储域 team_rooms、投影键 teamRoom、会话事件 team-room/fact 与设置槽位 team-rooms 必须保持字节级兼容以兼容旧数据;0.1.2-alpha.2 之后的事件词表变更为失败关闭,事实事件改走日志通道。按 Apache-2.0 协议分发,无任何模型限制,模型任意(房间不绑定模型路由)。
请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】,检查通过再动手。
插件:dsh-team-rooms(PerryLink/dsh-team-rooms)
仓库:https://github.com/PerryLink/dsh-team-rooms
本站详情页:https://www.yhbd.top/plugins/perrylink-dsh-team-rooms/
本站登记:类型 plugin · 归类 原生 DSH 插件 · 许可证 Apache-2.0 · ⭐ 4 · 最近提交 2026-09-25 · 主语言 JavaScript
按下面顺序执行,每步先把结论告诉我,再进入下一步:
【1 兼容性检查】
① 我这边:DSH 版本、Node 版本、操作系统、当前 profile(web / desktop)。
② 读它的 README、package.json、插件 manifest,列出它要求的 DSH 版本 / Node 版本 / 操作系统 / 外部依赖 / 需要另外先装的运行时。
③ 逐条比对,结论只写「满足 / 不满足 / 未知」三种;不满足的给出可行替代方案。
④ 检查是否和我已装的插件冲突:命令名重复、skill / tool 重名、端口占用、重复注册的 MCP server。
【2 安全性检查】
① 仓库可信度:和上面「本站登记」是否一致;star / fork 数、创建时间、最近提交,是否归档或长期停更。
② 安装脚本:逐行看 package.json 的 preinstall / install / postinstall,以及 install.sh、setup.ps1 之类脚本。出现 curl|bash、下载后直接执行、混淆代码、访问与插件功能无关的域名,立刻停下来告诉我,不要继续装。
③ 依赖:列出新增依赖,标出无人维护、或与知名包拼写近似的可疑包(typosquatting)。
④ 权限与副作用:它会读写哪些目录、访问哪些域名、需要哪些 DSH 权限(filesystem / network / shell / clipboard 等),以及怎么卸载和回滚。
⑤ 如果它要求 sudo / 管理员权限,或权限明显超出功能所需,先停下来问我。
【3 安装】
上面两步没有「不满足」和「高危项」时才执行;用官方推荐方式安装,不要自行提权。
【4 汇报】
用表格输出:检查项 / 结论 / 依据 / 是否需要我决策。拿不准的一律写「未知」并说明要我怎么确认——不要猜,也不要替我决定。
Send this message to DSH in your current session: it verifies compatibility and security first (answering met / not met / unknown item by item) and only installs once everything checks out — it will stop and ask you if it finds a high-risk item. The box scrolls; the copy is the full prompt. CLI install commands may not be accurate across systems, so DSH is the safer route.把上面这条消息直接发给当前会话里的 DSH:它会先核对兼容性与安全性(逐条给「满足 / 不满足 / 未知」),确认没问题再安装,有高危项会停下来问你。框内可滚动,复制到的是完整提示词;安装命令不一定准确,发给 DSH 更稳。
- Only 4 stars - very few users, little community feedback星标只有 4,几乎没人在用,遇到问题缺少社区反馈
DSH walks through these 9 checksDSH 会逐条核对这 9 项
Compatibility兼容性
- DSH, Node, OS and profile requirementsDSH 版本 / Node 版本 / 操作系统 / profile 是否满足要求
- External dependencies and runtimes (Electron / Python / Docker, ...)外部依赖与运行时(Electron / Python / Docker 等)是否齐备
- Conflicts with installed plugins: command names, skill / tool names, ports, duplicate MCP registration与已装插件是否冲突:命令名、skill / tool 重名、端口占用、重复 MCP 注册
Security安全性
- Repo matches the facts registered here; archived or abandoned?仓库是否与页面登记一致,是否归档或长期停更
- Safety of preinstall / install / postinstall and install.sh / setup.ps1preinstall / install / postinstall 与 install.sh、setup.ps1 是否安全
- curl|bash, download-then-execute, obfuscation, unrelated domains → stop immediatelycurl|bash、下载即执行、混淆代码、无关域名 → 立刻停止
- Typosquatting or unmaintained packages among the new dependencies新增依赖里有没有 typosquatting 或无人维护的包
- Requested permissions vs. what the feature actually needs申请了哪些权限、是否超出功能所需(filesystem / network / shell / clipboard)
- Any sudo / admin requirement, plus uninstall and rollback是否要求 sudo / 管理员权限,以及卸载与回滚方式
Anything uncertain must be marked unknown with a note on how to confirm it. This site's signal screen is a static snapshot, not a security audit.拿不准的必须标「未知」并说明要我怎么确认。本站的信号筛查是静态快照,不能替代安全审计。
Or use CLI install (for developers)或使用命令行安装(适合开发者)
CLI Install命令行安装
dsh plugin --profile web add dsh-team-rooms
把 PerryLink/dsh-team-rooms 加入你的 DSH 配置(web profile)即可启用。
READMEREADME
🏠 dsh-team-rooms
- 1024 store channel:
npm i -g dsh1024once, thendsh1024 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.
Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要,完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →
huxint/dsh-team
hanxuanliang/dsh-chaos
loopx-project/loopx
omdsh-dev/DSH-better-sidebar