ishuowang/dsh-agent-team-room

Name: ishuowang/dsh-agent-team-room
Author: ishuowang

Bundle捆绑包 Native原生 ⭐ 4 MIT Subagents & Orchestration子代理与编排 Models & Routing模型与路由 Sessions & Context会话与上下文

原生DSH房间，用于连接独立会话和提供商支持的AI成员——不捆绑角色或场景。

Project Overview项目介绍

Edited by Zhiwei Agent (zhiwei)由知微Agent(zhiwei)编辑

This is a native DSH bundle plugin that provides a coordinated conversation workspace for independent multi-agent sessions in DeepSeek Harness. It acts as coordination plumbing with a native cross-session timeline, and does not include built-in role templates, task boards, or standalone chat functionality. It extends DSH’s web UI with a dedicated Room tab alongside the default Chat tab, plus compact launchers for a native modal view. It only maintains persistent room identity, membership boundaries, and delivery metadata, and does not store duplicated copies of full session transcripts. All content displayed in the Room view is reconstructed on demand from existing DSH session logs.

Only the leader session that creates a room has permission to modify room membership, metadata, or close the room. Users can broadcast messages to all members or send direct messages to a single selected member, and all messages are ordered chronologically in the Room timeline view. This plugin is designed for DSH users who need to organize and manage structured multi-agent collaboration conversations within their existing DSH instance. Role management and task tracking are handled by separate integrated tools like RoleHub, so no fixed role system is mandated by this plugin. It keeps the core plugin lightweight and focused on its core coordination task.

This plugin is released under the open source MIT license. By default, it stores room metadata at $DSH_HOME/agent-team-room/rooms.json, falling back to ~/.dsh/agent-team-room/rooms.json if DSH_HOME is not set. The metadata file uses atomic writes with 0600 file permissions, and does not store any full message bodies, only delivery correlation data. Room does not sandbox third-party provider code, so users must avoid storing credentials or sensitive information in any room-related fields. To install from source, you can run npm ci then npm run check to verify the build before deployment. The repository prebuilds and commits the browser bundle, so no post-install build step is required for GitHub installs.

这是一个专为 DeepSeek Harness (DSH) 开发的原生插件包，提供支持独立会话和多AI成员协调的原生对话工作区。它本质是一套多智能体协调管线，带有原生跨会话时间线，不内置角色模板、任务看板，仅负责维护房间边界与会话元数据关联，不复制存储完整会话 transcript。

由创建房间的领导者会话维护房间所有权和成员权限，仅领导者可修改房间信息。支持广播或定向投递消息，通过原生UI的房间标签页展示按时间排序的对话时间线，所有内容都从现有DSH会话日志按需重构，适合需要管理多智能体协作对话的DSH用户使用。

该插件使用MIT许可证开源，默认将房间元数据存储在$DSH_HOME/agent-team-room/rooms.json，采用原子写入和0600权限，不存储消息正文。仅领导者可修改房间，不沙箱化第三方提供者代码，使用者需注意不要在房间信息中存放凭证或机密内容。

View on GitHub在 GitHub 查看

Send to your DSH发给你的 DSH 安装

请帮我安装这个 DSH 插件。安装前先完成【兼容性检查 + 安全性检查】，检查通过再动手。

插件：dsh-agent-team-room（ishuowang/dsh-agent-team-room）
仓库：https://github.com/ishuowang/dsh-agent-team-room
本站详情页：https://www.yhbd.top/plugins/ishuowang-dsh-agent-team-room/
本站登记：类型 bundle · 归类 原生 DSH 插件 · 许可证 MIT · ⭐ 4 · 最近提交 2026-09-04 · 主语言 TypeScript

按下面顺序执行，每步先把结论告诉我，再进入下一步：

【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 更稳。

Pre-install check安装前体检Compatibility · Security兼容性 · 安全性 1 warning1 项注意

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 github:ishuowang/dsh-agent-team-room#v0.6.0

把 ishuowang/dsh-agent-team-room 加入你的 DSH 配置（web profile）即可启用。

READMEREADME

20.5 KB · 缓存于 2026-09-04 19:40:32 · 20.5 KB

Agent Team Room

A native DeepSeek Harness conversation workspace for independent Sessions and provider-backed AI members.

Room is coordination plumbing with a native cross-Session timeline—not a team template, role library, task board, or standalone replacement chat app.

简体中文 · Install · Native UI · @ mentions · Commands · Provider SPI · AI support · Security

A Room is a durable, leader-owned membership boundary. It connects members that keep their own context and lifecycle, routes direct messages or broadcasts through the member's provider, and records bounded coordination metadata without copying Session transcripts. The native Room view reconstructs Room-addressed text and member replies from the backing DSH Session logs when they are available.

The v0.4 reset: built-in scenarios, embedded roles, tracked tasks, and the standalone dashboard are gone. To add a role, use an independent RoleHub bridge. To manage a Room, stay inside DSH's native UI.

One primitive, clear boundaries

flowchart LR
  L[Leader Session] --> R[Room core]
  R -->|built in| D[DSH Session provider]
  D --> C[Continuable direct-child Sessions]
  C --> S[Member Session logs]

  H[Trusted Host integration] -->|register provider| R
  RH[Optional RoleHub bridge] -->|verified role Session + provenance| H
  H --> X[Other member transports]

  UI[Native DSH Chat / Room tabs] --> V[Native Room workspace]
  E[Header / footer launchers] --> M[Native Room modal]
  R -->|membership + relay correlation| P[Conversation projection]
  S -->|Room-tagged turns + replies| P
  V -->|read-only text timeline| P
  M -->|read-only snapshot| R
  V -->|/room commands for writes| L
  M -->|/room commands for writes| L

Showing the opening section of the README — the full document lives in the repository以上为 README 开头摘要，完整文档在仓库内 · View the full README on GitHub →在 GitHub 查看完整 README →

渲染基于仓库 ishuowang/dsh-agent-team-room 的 README.md。在 GitHub 查看原文 →