Vai al contenuto principale
L

dsh-claude-project-ui

lanechenhku/dsh-claude-project-ui

Claude-style project UI for DeepSeek Harness on top of dsh-threads: one board gathering every project with its open threads and tasks, extra folders mounted per project via the native folder chooser, a bilingual zh/en panel with in-app settings, and thread reports rolled into tasks.

Installazione

dsh plugin --profile web add github:lanechenhku/dsh-claude-project-ui

README

dsh-claude-project-ui

简体中文 · English

把 Claude Code 的 Projects + Threads 体验搬进 DeepSeek Harness —— 在 @kyf-eng/dsh-threads 之上,补出 Claude 用户熟悉的那套 项目界面、交互方式和上下文逻辑。

一句话:dsh-threads 给出「项目 + 讨论串」的骨架;本插件补上 Claude 用户习惯的四件事—— 每个讨论串都懂的项目说明、一眼看完的看板面板、开新讨论串时的自动简报、 跨会话的上下文接续。

强化了 lead 与 thread 的分工

不只是补功能,还把这套分工调到位——主对话当 lead,讨论串当手:

  • 主对话会主动开 thread:默认不再先弹确认卡(offerApproval: "open"),判断该派活就直接派, 开完立刻回来陪你,不等、不轮询
  • 回报自动汇总:讨论串每轮回报自动变成看板任务(按 threadId 幂等去重),不用手工记账
  • 上下文自动交互:项目说明、看板快照、其它讨论串的进展,每个新 thread 第一步就带上
  • 并发上限 6 个讨论串(dsh-threads 默认 3 个,满了会回「或者这件事在主对话里做」)
  • 目标是把 **Claude Code(Opus 5.5 一代)**那套项目体验尽量搬过来:项目 → 讨论串 → 汇报 → 继续派活

让这套分工生效的两行配置

本插件不改 dsh-threads 的提示词;分工效果来自 dsh-threads 自己的 dispatcher prompt + 下面两个开关:

- id: dsh-threads
  name: '@kyf-eng/dsh-threads'
  config:
    offerApproval: "open"   # 用户点名任务但没明说开 thread 时,直接开、不弹确认卡
    maxRunning: 6           # 同时最多 6 个讨论串(默认 3)

改完完全退出 DSH 再启动。

和 dsh-threads 的关系:补强,不是替代

能力@kyf-eng/dsh-threads本插件 dsh-claude-project-ui
项目 / 讨论串的创建与生命周期✅ 拥有只读识别,绝不写它的数据
主对话当 lead、主动开 thread✅ 提示词 + thread_open—
项目级说明(每个 thread 都看到)❌ 只有主对话自己的 instructions✅ 短约定注入主对话和所有讨论串
跨 thread 的看板❌✅ 侧栏面板 + /hub board 命令 + board_list 工具
开 thread 时的上下文简报手写 task 文本✅ context_brief 一键拼好
讨论串回报汇聚成任务❌✅ 幂等自动汇总(按 threadId 去重)
讨论串建好时的启动上下文—✅ 自动注入项目说明 + 看板 + 他人进展
辅助文件夹(多目录挂载)PR #61 在做,未发布✅ 本插件自己存 + 提示注入 + 沙箱可写根
切换项目主文件夹PR #61 在做,未发布✅ 本插件实现(写 dsh-threads 记录 + DSH workspace 记录,重启后新会话生效)

两个插件通过存储文件 + storage-domain 写链解耦:本插件不 import dsh-threads 的模块,平时只读它的存储; 只有「切换主文件夹」这一条写路径(src/mainfolder.js)会动它的项目记录和 DSH 的 workspace 记录, 而且走 dsh-threads 已经打开的 domain 句柄、带备份与回滚。任何一个卸载,另一个照常工作; dsh-threads 换存储格式时本插件静默降级为「不注入」,不会报错。

比 Claude Projects 多出的东西

同一件事(项目 / 讨论串 / 任务),Claude Projects 有一套原设计;在 DSH 里,这套东西的形状不太一样。 下表只列代码里确实做到、并且和原设计有差别的几处,每行一句,细节在下面各节。

能力Claude Projects本插件
项目总览项目列表,进项目才看得到会话侧栏一屏铺开所有项目:当前项目置顶卡(左侧强调条),其余按最近活动倒序,每行带讨论串数 / 任务数 / 最近活动时间
多目录挂载一个项目一个工作目录项目可再挂多个辅助文件夹:每个会话登记为沙箱可写根(宿主提供沙箱策略时),新会话的提示里直接给绝对路径,kb_add 只在主文件夹与已挂载目录里取文件
文件夹入口项目设置一处三个入口共用同一个弹窗、同一条写入路径:看板卡「更换…」、设置页逐项目一行、讨论串设置里的「⚙ 更多文件夹⋯」
看板设置没有看板设置看板右上 ⚙:语言、显示已解决/已归档、回报汇总、「其他项目」卡片默认折叠/展开、排序、文件夹管理——改完立即生效,存在本插件自己的 settings.json 里,不改配置、不重启
中英切换界面语言跟随应用97 条文案中英各一份,可在 ⚙ 里锁定中文或 English,切换当下重渲染,不用改 cordis.yml
回报变任务没有跨会话任务看板讨论串每轮回报按 threadId 幂等汇总成任务(done / doing / pending / blocked),已解决的讨论串不再生成新任务
选文件夹建项目或换目录时选一次切换主文件夹、每次加辅助文件夹都能弹系统原生选择框(Desktop 走 Electron 对话框,其余环境走宿主 picker);拿不到选择器就不渲染按钮,手输路径照旧

这不是「替代 Claude Projects」——两个是不同产品(本插件运行在 DeepSeek Harness 上,需要 dsh-threads), 表里只说明同类需求在这里怎么解;没有代码支撑的对比不写。

功能

知识库

工具作用
kb_add加一篇文档(同标题=替换);正文可内联,也可给 path 读文件
kb_list列出 id、标题、字数、标签
kb_search中英混合检索(CJK 二元组 + 英文词),返回片段和文档 id
kb_get按 id 读全文,可分页(offset/limit)
kb_remove删除一篇

上限:每项目 200 篇 / 400 万字 / 单篇 40 万字(可在配置里调)。

看板

讨论串状态由 dsh-threads 持有,本插件只读:#3 补文档 — 待决策 · dsh-threads/3-ab12cd。 手动任务独立存放(b-<n>),可改状态 pending / doing / blocked / done。

工具作用
board_add / board_update增/改手动任务(讨论串也可以用来报自己的进度)
board_list合并视图:讨论串实时状态 + 手动任务
hub_note记一条项目级上下文(决策、约束),所有会话可见

上下文

入口作用
context_brief 工具 / /hub brief生成项目简报,粘进 thread_open.task
自动注入每个项目会话(主对话 + 讨论串)都会收到:知识库索引、看板快照、最近进展(含其它讨论串的回报)

命令

/hub status                  我在哪个项目、多少知识/任务
/hub board [--all]           看板(默认隐藏已解决/已归档的讨论串)
/hub task <标题>              加一条手动任务
/hub done <b-N>              把任务标记为完成
/hub rm <b-N>                删除任务
/hub doctor                  自检:数据目录、讨论串存储、注入预算
/hub kb [关键词]              知识库列表或检索
/hub brief                   项目简报
/hub note <文本>              记一条项目级上下文
/hub folders [add|rm <路径>]  辅助文件夹:列出 / 挂载 / 移除
/hub folder [<路径>]         看 / 切换项目主文件夹(当前对话不动,重启后新会话才用新目录)
/hub add <标题> | <正文>      加一篇知识库文档(正文可省略)

一次粘多行也可以:每条以 /hub 开头(或只是首行带 /hub),逐行执行、逐条汇报。 行尾的 → 说明 会被当作注释丢掉。

看板面板(侧栏)

浏览器半会往右侧栏加一个「项目看板」页签,和 dsh-threads 的「讨论串」并列(会话头部还有一个「▤ 项目看板」按钮可以一键打开)。 版式是两层的,不再是一堆项目平铺:

  • 顶部:当前项目一张独立卡片。左侧 3px 强调色竖条 + 项目名 + monospace 小字路径; 右上「切换文件夹⋯」打开共用弹窗,右侧箭头展开/收起讨论串与任务;卡片内还有「辅助文件夹(N)」折叠区。 「当前项目」= 打开面板时所在那个对话所属的项目(面板把会话 id 发给宿主,宿主查 dsh-threads 记录解析); 解析不出来就不强行置顶,下面直接按活跃度排。
  • 分隔:一条 2px 粗分隔 + 文字「其他项目 · N」(英文 Other projects · N),滚动时吸顶。
  • 其他项目:按最近活动时间(项目记录与它所有讨论串里最新的那个)倒序,每个项目一行紧凑卡片 (名称 + 讨论串/任务数量 + 最近活动时间),点开才展开讨论串与任务行;卡片之间是 1px 细线 + 12px 间距。
  • 讨论串行 = 状态点(6px)+ #编号 + 标题(单行省略)+ 右侧状态词。 状态点颜色:进行中=蓝、待办=灰、受阻/待决策=橙、已完成/已解决=绿、空闲/已停止=浅灰。
  • 任务行 = 状态 pill + 任务号 + 主题 + 右侧「+」(复制任务号,/hub done <id> 用)。
  • 空状态只留一行浅色提示,不占大块;「刷新」重新拉取。
  • 数据来自宿主半的 POST /project-hub/board,只读。
  • 头部「刷新」左边有一个 ⚙ 看板设置(同一套 portal 的紧凑面板,宽 360): 语言(跟随应用 / 中文 / English,手动选择优先于应用语言,括号里显示当前应用语言)、 显示已解决 / 已归档的讨论串(默认关)、自动把讨论串回报汇总成任务(默认开)、 「其他项目」卡片默认折叠 / 展开、排序(最近活动 / 名称)、以及「项目文件夹管理…」。 改完立刻生效并持久化,不需要重启;存在本插件自己的 settings.json 里(不写 dsh-threads 的存储)。 其中「隐藏讨论串」和「回报汇总」是宿主侧行为,所以宿主也读同一份设置。

视觉规范(不改主题也深浅两套都能看):8px 网格间距、圆角 10、边框 rgba(127,127,127,0.18)、 hover 背景 rgba(127,127,127,0.06)、不用大阴影、字号 12/13、路径用 monospace 11。

面板只在 Web GUI(desktop / web profile)出现;tui / headless 没有侧栏, 退化成 /hub board 命令和 board_list 工具。

辅助文件夹(多目录挂载)

一个项目除了主文件夹,还可以挂载多个辅助文件夹(类似 Claude Code 的 additional directories)。 在「▤ 项目看板」当前项目卡片的「辅助文件夹」折叠区里、或在文件夹弹窗里增删,也可以用命令:

/hub folders                 列出已挂载的辅助文件夹
/hub folders add <绝对路径>   挂载一个(也接受 ~/ 开头的写法)
/hub folders rm <绝对路径>    移除一个

行为与边界:

  • 存本插件自己的数据:projects/<id>/folders.json。绝不写 dsh-threads 的 dsh_threads.json, 两边各管各的存储,删掉任一插件另一边照常读。
  • 路径落盘前归一化为物理绝对路径(realpath):DSH 沙箱不接受用 symlink 拼写的额外根, 非目录 / 读不到的路径直接拒绝。
  • 系统提示给每个项目会话(主对话 + 每个讨论串)列出挂载目录(project-hub/folders section)。
  • 沙箱:宿主半对项目里每个存活会话调用 ctx.sandboxPolicy.registerWritableRoot(session, dir), 所以 workspace-write 下核心文件工具与 bash 都能写这些目录。授权是运行时、按会话的: 重启 / resume / fork 后由 10 秒的刷新循环重新登记;read-only 不授予写权限; Windows 上进程隔离不认额外根(只有 harness 的文件工具认)。
  • 我们自己的文件工具认这些目录:kb_add 的 path 只允许主文件夹和已挂载目录里的文件, 其它路径会报错并列出当前可用的挂载(它用插件自己的权限读盘,所以这条校验必须自己兜住)。
  • 授不到沙箱根时(宿主没有 sandboxPolicy 服务、目录被删、或不是目录)面板会明确标注, 不会假装挂载可用。

切换主文件夹(重启后生效)

面板里「主文件夹」那一行的「切换文件夹…」按钮(或 /hub folder <绝对路径>)会打开系统的文件夹选择器; 没有选择器时可以在同一块里手填绝对路径。选完之后:

  • 两处记录一起改,缺一不写:

    • ~/.dsh/storages/dsh_threads.json → tables.projects[<id>].folder:dsh-threads 渲染那栏 UI 用它,本插件面板也直接读它(不另存一份真相);
    • ~/.dsh/storages/workspace.json → tables.workspaces[<workspaceId>].path:新会话的目录是从这里读的。 只改第一处会出现「面板显示新目录、新会话还在旧目录」的假切换,所以第二处写不进去时整次切换直接失败、什么都不改。
  • 写之前备份:两个存储文件各留一份 <文件>.bak-mainfolder-<时间戳>; 写入走 dsh-threads / DSH 已经打开的那个 storage-domain(内存态是权威、写链串行), 宿主没暴露该服务时退化为「重新读取 → 原子 rename」,并在面板上标注这次是直写文件。

  • 校验:目标必须存在且是目录,realpath 归一化(去尾斜杠、解 symlink); 拒绝 /、/Applications、/System、/Library、/usr 等系统目录,拒绝用户主目录本身、 ~/.dsh(含子目录)、~/.ssh 与本插件自己的数据目录;目标目录已被另一个 DSH workspace 占用时也拒绝 (否则 DSH 启动时的 workspace 一致性检查会失败)。

  • 失败不静默:写后读回校验,不一致或中途抛错就回滚两处记录,并把原因(含备份路径)显示在面板上。

  • 生效边界(实话):DSH 把 workspace 记录缓存在进程内存里,所以

    新会话和新讨论串要等 DeepSeek Harness 重启之后才用新文件夹;当前这个对话在你重启前仍留在原目录。

    本插件的写入路径从不改活动会话的工作目录(src/mainfolder.js 里只写那两条记录),这就是「当前对话不动」的由来。 面板与 /hub folder 的文案都按这个语义写,不会说「立即生效」。

  • 耦合风险:dsh_threads/workspace 的 domain 名与字段是 dsh-threads 和 DSH 的私有契约; 上游 PR #61 合并后应改用它提供的官方入口。字段变了会在切换时直接报错并回滚(不会写坏记录)。 详见 docs/folders-feasibility.md。

文件夹的三个入口(同一套组件、同一条写入路径)

改文件夹有三处,行为一致:都打开同一个弹窗,都走宿主半 src/mainfolder.js 那一条写入路径 (备份 → realpath → 校验 → 串行 → 读回 → 失败回滚),没有第二套实现。

入口位置作用范围
A看板里当前项目卡片的「切换文件夹⋯」+「辅助文件夹」折叠区只作用当前项目
B设置页新分节「项目文件夹 / Project folders」逐行改任意一个项目或工作区
Cdsh-threads 自己的「项目设置 → 通用 → 文件夹」卡片里注入的「⚙ 更多文件夹⋯」打开的那个项目

三处都写明同一件事:

改动会写入 dsh-threads 的项目记录与 workspace 记录;dsh-threads 自己的设置面板要重启 DSH 之后才同步显示 (它读自己的 client store,不订阅存储变更)。

细节:

  • B 刻意没有「批量改全部」:一次误点就会冲掉十几个项目记录,所以只做逐个修改。 项目行会同时改项目记录与工作区记录;工作区行只改工作区记录。 已经被项目占用的工作区不能单独改——请求会被拒绝并提示去项目那一行改,两处记录必须一起动; 没有项目用的工作区才可以单独改(只动 workspace.json,同样有备份 / 读回 / 回滚)。
  • C 的注入约束:MutationObserver 在 dsh-threads 的文件夹卡片里找 .dsht-setting-path 锚点, 找不到就静默不注入;重复触发幂等(同一个卡片永远只有一个按钮,文案跟着语言刷新); 所有 DOM 读写都包在 try/catch 里,dsh-threads 的 DOM 结构变了最多掉按钮,绝不抛到宿主、不会白屏。 卡片里显示的是那个项目的文件夹路径,按钮据此在项目记录里认领项目再打开同一个弹窗。

文件夹弹窗(0.4.1 起)

三个入口打开的是同一个弹窗,结构固定,只有这几块:

项目名(粗体)
当前主文件夹
/Users/me/code/app                       ✕
[更换…]  手动输入路径                       已保存(2 秒)
──────────────────────────────────────────────
辅助文件夹  (2)
  ▱ /Users/me/data              [移除]
  ▱ /Users/me/notes             [移除]
  [/Users/me/another____]  [浏览…]  [添加]
辅助文件夹会登记为每个会话的沙箱可写根;改动写入 dsh-threads 记录,其设置面板重启后同步。
  • 弹窗portal 到 document.body(容器 #project-hub-dialog-root,role="dialog" / aria-modal="true"), 所以不会被面板、设置页或 dsh-threads 自己的 Modal 压住——position: fixed 的 z-index 只在当前层叠上下文里比大小, 而宿主的父级只要有一个 transform 就能把弹窗困在下面。
  • 打开时锁 body 滚动;Esc 关闭、点遮罩关闭。
  • 成功反馈只有「已保存」,2 秒后自己消失;没有 toast,没有 alert,没有大段说明。
  • 路径单行省略,鼠标悬停显示全路径。
  • 「浏览…」(0.4.1 起,辅助文件夹那一行):点了弹 DSH 自己用的原生文件夹选择器——Desktop 应用里走 window.__DSH_DIRECTORY_PICKER__(Electron dialog.showOpenDialog),其余环境走宿主 uiWorkspace.pickDirectory()。选中只把绝对路径填进输入框,仍要按「添加」才写入。 宿主没有选择器时按钮压根不渲染;中途失败则静默收起,手输路径照旧。 两条链路的证据(主进程 / preload / 渲染端消费点)见 docs/native-directory-picker.md。
  • 更长的解释(沙箱授权语义、重启边界、两处记录为什么要一起改)都在本文档下面的章节里,弹窗里只剩一行脚注。

双语(跟随应用语言)

怎么切成英文:侧栏底部「设置」→「通用」→「语言」那一行 → 选 English(语言项由 DSH 自己的 dsh-client-locale 提供,切换后其它插件与内核文案一起换)。切完不用刷新:本插件的面板、弹窗、 设置页、注入按钮会立刻重渲染。

面板、弹窗、设置页和注入按钮的所有文案都在 src/client.js 的 MESSAGES.zh / MESSAGES.en 两张表里 (各 97 个 key;测试会校验两侧 key 完全一致、没有空文案、并且没有「表里有但没地方用」的 key):

  • 语言来自 DSH 的 locale 服务(dsh-client-locale):ctx.locale.getLocale() 读当前语言、 ctx.on("locale/change") 跟随切换、ctx.locale.register("project-hub", { zh, en }) 登记字典。 切换语言后面板 / 弹窗 / 设置页立刻换文案,不用刷新。
  • 缺 key 时的回退顺序:当前语言 → 英文 → 中文 → key 本身。英文是兜底,所以漏翻译只会退回英文, 不会露出 board.section.others 这种原始 key。
  • 侧栏页签标题这类由宿主渲染的文字用 thunk 提供,宿主下次渲染时跟上新语言。

安装

需要 DeepSeek Harness 0.2.1-rc.2 到 0.3.0。

桌面 App(desktop profile)

不要用 dsh plugin --profile desktop ...:desktop profile 由 Electron 独占,命令行会被 无条件拒绝(profile "desktop" is managed exclusively by the Electron application), 和 App 有没有在运行无关。

两条可用路径:

  1. 设置 → 插件 → 市场,搜索 dsh-claude-project-ui 安装,然后重启。
  2. 手工安装(离线或私发 tarball 时):
# 解到 profile 的 node_modules
mkdir -p ~/.dsh/profiles/desktop/node_modules/dsh-claude-project-ui
tar xzf dsh-claude-project-ui-0.2.0.tgz -C /tmp/pkg
cp -R /tmp/pkg/package/. ~/.dsh/profiles/desktop/node_modules/dsh-claude-project-ui/

然后编辑 ~/.dsh/profiles/desktop/package.json:dependencies 里加 "dsh-claude-project-ui": "^0.2.0",dsh.profile.bundles 数组里追加 "dsh-claude-project-ui", 最后完全退出 DSH(⌘Q)再启动。

只加依赖、不加 dsh.profile.bundles 不会加载——DSH 只从 bundles 层挂载插件。

其他 profile(web / tui / 自建)

这些 profile 由 CLI 启动,可以正常用插件管理器:

dsh plugin --profile web add dsh-claude-project-ui

卸载

桌面 App:从 dependencies 和 dsh.profile.bundles 里删掉,再删 ~/.dsh/profiles/desktop/node_modules/dsh-claude-project-ui,重启。 其他 profile:dsh plugin --profile web remove dsh-claude-project-ui。

数据留在 ~/.dsh/project-hub/,卸载不会删;要彻底清掉就删这个目录。

快速开始(3 步)

装好并完全退出 DSH 再启动之后:

/hub status        我在哪个项目、多少知识 / 任务
/hub note 发布前必须跑 node test/harness.mjs
/hub add 发布清单 | 1) 跑测试 2) npm pack 3) gh release
/hub brief         粘进 thread_open.task 的项目简报

右侧栏「▤ 项目看板」页签里应该能看到刚加的任务和讨论串状态;tui / headless 没有侧栏,用 /hub board。 开新讨论串时它第一步就会带上项目说明、看板快照和最近进展,不用你复制粘贴。

配置

在 profile 的 cordis.patch.yml 里覆盖:

- id: dsh-claude-project-ui
  name: "dsh-claude-project-ui"
  config:
    dataDir: ""                      # 默认 ~/.dsh/project-hub
    threadsStorage: ""               # 默认 ~/.dsh/storages/dsh_threads.json
    workspaceStorage: ""             # 默认与 threadsStorage 同目录的 workspace.json(切换主文件夹时写)
    knowledgeIndexMaxChars: 280
    kbIndexMaxDocs: 3
    boardContextMaxChars: 700
    digestContextMaxChars: 700
    maxExtraFolders: 8               # 一个项目最多挂载几个辅助文件夹
    foldersContextMaxChars: 600      # 注入的挂载目录列表字符上限
    briefMaxChars: 4000
    maxNotes: 200
    maxDocs: 200
    maxKnowledgeChars: 4000000
    hideResolvedThreads: true        # 看板与注入里隐藏已解决/已归档的讨论串
    autoConvergeReports: true        # 把讨论串回报自动汇总成看板任务(幂等)
字段默认值影响
dataDir~/.dsh/project-hub知识库 / 任务 / 笔记的根目录;换掉就是另一套项目数据
threadsStorage~/.dsh/storages/dsh_threads.json只读;用来识别「哪些会话属于哪个项目」,格式变了会静默降级为不注入。切换主文件夹时这一处也会被写(见上)
workspaceStorage与 threadsStorage 同目录的 workspace.json只在切换主文件夹时写:新会话的目录来自这里的 workspaces[].path;指错会让切换失败并回滚
knowledgeIndexMaxChars280注入的知识库索引字符上限;调大占提示词预算,调小了只列更少文档
kbIndexMaxDocs3索引里最多列几篇文档,其余提示用 kb_search 检索
boardContextMaxChars700注入的看板快照字符上限
digestContextMaxChars700注入的「最近进展」字符上限
maxExtraFolders8一个项目最多挂载几个辅助文件夹
foldersContextMaxChars600注入的辅助文件夹列表字符上限
briefMaxChars4000context_brief / /hub brief 的单次输出上限
maxNotes200每个项目保留多少条 hub_note 进展笔记
maxDocs200每个项目允许的知识库文档数
maxKnowledgeChars4000000每个项目知识库总字符数上限
hideResolvedThreadstrue初始值:⚙ 里「显示已解决 / 已归档的讨论串」;设置文件一旦存在以它为准。board_list all=true 单次仍可看全部
autoConvergeReportstrue初始值:⚙ 里「自动把讨论串回报汇总成任务」(按 threadId 幂等)

数据

~/.dsh/project-hub/settings.json          看板设置(语言/隐藏/汇总/卡片/排序;本插件自己的)
~/.dsh/project-hub/projects/<projectId>/
  knowledge.json   知识库文档
  board.json       手动任务
  notes.json       项目上下文笔记
  folders.json     辅助文件夹挂载(本插件自己的记录)

全部是普通 JSON,原子写入(临时文件 + rename),可以手工备份或编辑。

切换主文件夹不改这里,而是改 ~/.dsh/storages/dsh_threads.json 与 ~/.dsh/storages/workspace.json (写前各留一份 *.bak-mainfolder-<时间戳>)。

已知限制

  • 只读识别 dsh-threads 的存储文件;它的存储格式若改变,项目识别会失效(插件会静默降级为「不注入」而不是报错)。
  • 知识库是词法检索(CJK 二元组 + 英文词 + 词频归一化),没有向量检索,也没有 LLM 摘要;文档要自己写清楚标题和关键词。
  • 摘要不是模型生成的:自动部分来自 dsh-threads 的 lastReport,手动部分来自 hub_note。主对话自己没回报过的东西不会出现。
  • 注入内容按字符截断(每段默认 700-900 字),不是按 token 精确计量。
  • 面板除了辅助文件夹增删和主文件夹切换以外是只读的:建/改/删任务目前只能用 board_add / board_update / /hub task|done|rm。
  • 主文件夹切换依赖 dsh_threads / workspace 两个 storage domain 的私有字段(dsh-threads 与 DSH 的契约)。 上游 PR #61 合并后应改用它提供的入口;字段变了对不上时切换会报错并回滚,不会静默写坏。
  • 主文件夹切换当前对话不搬家:只有重启 DSH 之后新建的会话 / 讨论串才用新目录;面板与 /hub folder 都这么写。
  • 辅助文件夹的沙箱授权只在 workspace-write 生效;read-only 下核心工具本来就写不了。 授权是运行时状态,重启 / resume 后需要重新登记(刷新循环会自动做,最多延迟 10 秒)。
  • 轮询刷新:每 10 秒 + agent 状态变化时刷新提示词快照,最坏情况看到的是 10 秒前的看板。
  • 看板默认隐藏已解决/已归档的讨论串(⚙ 里可以打开);一次性看全部用 board_list all=true 或 /hub board --all。
  • 配置里的 hideResolvedThreads / autoConvergeReports 现在是初始默认值:⚙ 里一改就以设置文件为准。
  • ⚙ 面板的「项目文件夹管理…」不跳转设置页:DSH 没有公开「打开设置页某个分节」的客户端 API, 它在同一个面板里渲染同一个管理组件(逐行修改,没有批量)。

验收记录(2026-11-18,本机 desktop profile)

层结论证据
命令通过会话日志 command/run + command/done;多行 5 条、add | 正文 均生效;knowledge.json 落盘
工具通过项目主对话里模型经 PTC 调用 tools.kb_search({query:"release"}),返回 [k-1] 发布清单 score=0.343
注入通过(知识库)真实 system prompt 中出现:本项目共享知识库(主对话和每个讨论串都会收到这份索引)。\n## 项目知识库(1 篇…)
注入(看板/进展)通过讨论串 #2 的请求体(user/message 记录,12.7KB)里逐字包含 ## 项目看板、两行讨论串状态、## 项目进展 段;KB 则在 system/message 里(section vs context 两种注入通道)
schema 兼容通过node test/spec-check.mjs 对照宿主 DSL 校验 10 个工具定义
逻辑通过node test/harness.mjs 30 项(含 changedFiles、隐藏规则、汇总幂等、/hub doctor、extraFolders 持久化 / 提示注入 / kb_add 目录校验 / 文件夹路由鉴权、主文件夹切换(两处记录 / 备份 / 拒绝非法路径 / 并发不丢数据 / 回滚)/ /hub folder / 路由)

与 Team 模式的关系

Team 模式的任务板属于单个会话的 subagent 树;本插件的看板属于一个 dsh-threads 项目(主对话 + 它的所有讨论串)。两者互补,不会互相写入。

License

MIT(见 LICENSE)。


dsh-claude-project-ui (English)

Bring the Claude Code Projects + Threads experience to DeepSeek Harness. On top of @kyf-eng/dsh-threads, this plugin adds the project UI, the interaction model and the context logic Claude users expect.

In one line: dsh-threads provides the "project + thread" skeleton; this plugin adds the four things Claude users are used to — a project brief every thread can see, a board you can read at a glance, an automatic brief when a thread is opened, and context that carries over between sessions.

A sharper lead / thread split

This is not only extra features — it tightens the division of labour so the main conversation leads and threads do the hands-on work:

  • The main conversation opens threads on its own: with offerApproval: "open" it no longer asks for confirmation first, delegates when it judges the work belongs in a thread, and returns to you immediately without waiting or polling
  • Reports roll up automatically: each thread report becomes a board task (idempotent, keyed by threadId) — no manual bookkeeping
  • Context flows without you: project brief, board snapshot and other threads' progress are attached to every new thread from its first step
  • Up to 6 concurrent threads (dsh-threads defaults to 3, and at the cap it answers "or do the work in the main conversation")
  • The goal is to bring the Claude Code (the Opus 5.5 generation) project experience over as closely as possible: project → threads → reports → keep delegating

The two settings that make it behave this way

This plugin does not touch dsh-threads' prompt; the behaviour comes from that plugin's own dispatcher prompt plus these two switches:

- id: dsh-threads
  name: '@kyf-eng/dsh-threads'
  config:
    offerApproval: "open"   # open the thread right away instead of asking first
    maxRunning: 6           # up to 6 concurrent threads (default 3)

Quit DSH completely and start it again after editing.

Relationship to dsh-threads: a complement, not a replacement

Capability@kyf-eng/dsh-threadsThis plugin dsh-claude-project-ui
Project / thread creation and lifecycle✅ owned thereRead-only detection, never writes its data
Main conversation as lead, opening threads✅ prompt + thread_open—
Project-level instructions every thread sees❌ main conversation only✅ short rules injected into the main conversation and every thread
Cross-thread board❌✅ sidebar panel + /hub board + board_list tool
Brief when opening a threadhand-written task text✅ context_brief assembles it
Thread reports rolled up as tasks❌✅ idempotent rollup keyed by threadId
Startup context for a new thread—✅ project brief + board + other threads' progress
Auxiliary folders (additional directories)PR #61, unreleased✅ own record + prompt list + sandbox writable roots
Switching the project main folderPR #61, unreleased✅ implemented here (writes the dsh-threads project record + the DSH workspace record; new sessions follow after a restart)

The two plugins are decoupled through storage files plus a storage-domain write chain: this plugin never imports dsh-threads modules and normally only reads its storage. Exactly one write path — switching the main folder (src/mainfolder.js) — touches dsh-threads' project record and DSH's workspace record, through the domain handle dsh-threads already opened, with a backup and a rollback. Uninstalling either leaves the other working; if dsh-threads changes its storage format, this plugin silently degrades to "no injection" instead of throwing.

What goes beyond Claude Projects

The same job — projects, threads, tasks — but shaped a little differently in DSH. Only the differences the code actually implements, one line each; the sections below carry the detail.

CapabilityClaude ProjectsThis plugin
Project overviewA project list; sessions appear after you open oneEvery project on one sidebar page: the current project on a top card with an accent rail, the rest ordered by last activity, each row carrying thread count / task count / last active
Extra foldersOne working directory per projectA project can mount extra folders: each session gets them as writable sandbox roots (when the host exposes a sandbox policy), new sessions are told the absolute paths, and kb_add only reads inside the main folder or a mounted one
Folder entry pointsProject settings onlyThree entries share one dialog and one write path: "Change…" on the board card, one row per project on the settings page, and "⚙ More folders…" in dsh-threads' own settings card
Board settingsNone⚙ at the top of the board: language, show resolved/archived, roll reports into tasks, other cards collapsed/expanded by default, sort, folder management — applied immediately and stored in this plugin's own settings.json, no config edit, no restart
BilingualUI follows the app language97 strings in both tables; pin 中文 or English in ⚙ and the panel re-renders at once, no cordis.yml edit
Reports become tasksNo cross-session task boardEach thread report becomes a task, deduplicated by threadId (done / doing / pending / blocked); resolved threads stop creating new ones
Choosing a folderPick once when creating or moving a projectBoth the main-folder switch and every "add extra folder" can open the OS folder chooser (Electron dialog on Desktop, the host picker elsewhere); with no chooser the button is not rendered and a typed path still works

Not a claim of replacement: this plugin runs on DeepSeek Harness and needs dsh-threads. The table only says how the same needs are solved here; anything without code behind it is left out.

Features

Knowledge base

ToolPurpose
kb_addAdd a document (same title = replace); inline body, or a path to read from disk
kb_listList id, title, size and tags
kb_searchMixed Chinese/English retrieval (CJK bigrams + English words); returns snippets and document ids
kb_getRead one document by id, paginated (offset / limit)
kb_removeDelete a document

Limits: 200 documents, 4M characters and 400k characters per document, per project (configurable).

Board

Thread state is owned by dsh-threads and read-only here: #3 write docs — needs decision · dsh-threads/3-ab12cd. Manual tasks live separately (b-<n>) with statuses pending / doing / blocked / done.

ToolPurpose
board_add / board_updateCreate or update a manual task (threads can use it to report their own progress)
board_listMerged view: live thread state plus manual tasks
hub_noteRecord one line of project context (a decision, a constraint) visible to every session

Context

Entry pointPurpose
context_brief tool / /hub briefCompose the project brief and paste it into thread_open.task
Automatic injectionEvery project session (main conversation and each thread) receives: the knowledge index, a board snapshot and recent progress from other threads

Commands

/hub status                  Which project am I in, how much knowledge / how many tasks
/hub board [--all]           The board (resolved/archived threads hidden by default)
/hub task <title>            Add a manual task
/hub done <b-N>              Mark a task done
/hub rm <b-N>                Delete a task
/hub doctor                  Self-check: data dir, thread storage, injection budget
/hub kb [query]              List the knowledge base, or search it
/hub brief                   Project brief
/hub note <text>             Record one line of project context
/hub folders [add|rm <path>] Auxiliary folders: list / mount / unmount
/hub folder [<path>]         Show / switch the project main folder (this conversation stays put; new sessions after a restart)
/hub add <title> | <body>    Add a knowledge document (body optional)

You can paste several lines at once: each line starts with /hub (or only the first line does), and they run in order with a per-line report. A trailing → note is treated as a comment.

Board panel (sidebar)

The browser half registers a tab in the right-hand sidebar pane, next to dsh-threads' thread list (the session header also gets a "▤ Project board" button that opens it). The layout has two layers instead of one flat list of projects:

  • Top: the current project, one card of its own. A 3px accent rail on the left, the project name, the path in 11px monospace; "Change folder…" in the top right opens the shared dialog, the chevron expands the thread and task rows, and an "Auxiliary folders (N)" section collapses underneath. "Current" means the project of the conversation the panel was opened next to: the panel sends its session id, the host resolves it against dsh-threads' records. When nothing resolves, no card is promoted and the list is simply ordered by activity.
  • Divider: a 2px rule carrying "Other projects · N" that sticks to the top while scrolling.
  • Other projects sort by newest activity (the newest of the project record and all its threads) and each is a compact card — name, thread and task counts, last active — that expands into its rows on click. Cards are separated by a 1px hairline plus 12px of space.
  • Thread row = 6px status dot + #n + title (single line, ellipsised) + state word on the right. Dot colours: running = blue, to do = grey, blocked / needs a decision = orange, done / resolved = green, idle / stopped = light grey.
  • Task row = status pill + task id + subject + a "+" on the right that copies the id for /hub done <id>.
  • An empty state is one faint line, not a block; "Refresh" reloads.
  • Data comes from the host half's POST /project-hub/board and is read-only.
  • Left of "Refresh" there is a ⚙ board settings popover (the same portal, 360px wide): language (follow the app / 中文 / English — a manual choice beats the app language, and the follow option shows the current app language in parentheses), show resolved and archived threads (off by default), roll thread reports into tasks (on by default), whether "other projects" cards start expanded, the sort order (last active / name), and "Manage project folders…". Every change applies immediately and is persisted, no restart: it lives in this plugin's own settings.json, never in dsh-threads' storage. Hiding threads and rolling up reports are host-side behaviours, so the host reads the same file.

Visual rules (both themes, without touching the theme): 8px spacing grid, radius 10, border rgba(127,127,127,0.18), hover wash rgba(127,127,127,0.06), no large shadows, type at 12/13px, paths in 11px monospace.

The panel only exists in the Web GUI (desktop / web profiles). tui and headless have no sidebar and fall back to the /hub board command and the board_list tool.

Mounted folders (additional directories)

A project can mount extra auxiliary folders on top of its main folder (Claude Code's additional directories idea). Add or remove them in the current-project card's "Auxiliary folders" section, in the folder dialog, or by command:

/hub folders                 list mounted folders
/hub folders add <path>      mount one (absolute, or ~/…)
/hub folders rm <path>       unmount one

Behaviour and boundaries:

  • This plugin's own record: projects/<id>/folders.json. It never writes dsh-threads' dsh_threads.json; each plugin owns its data and removing either leaves the other readable.
  • Paths are stored as physical absolute paths (realpath): the DSH sandbox rejects an extra root spelled through a symlink; missing or non-directory paths are refused.
  • System prompt: every project session (main conversation and each thread) gets the mount list as a project-hub/folders section.
  • Sandbox: the host half calls ctx.sandboxPolicy.registerWritableRoot(session, dir) for every live session of the project, so under workspace-write the core file tools and bash can write those directories. Grants are runtime-only and per session: the 10-second sweep re-registers them after a restart / resume / fork. read-only grants no writes; on Windows process confinement ignores extra roots (the harness file tools honour them).
  • Our own file tool honours them: kb_add's path accepts files under the main folder and the mounted folders only; any other path fails with the available mounts listed (it reads with the plugin's own rights, so it enforces the boundary itself).
  • When a grant cannot be made (no sandboxPolicy service, a deleted directory, a non-directory), the panel says so explicitly instead of pretending the mount works.

Switching the main folder (effective after a restart)

The "Change folder…" button on the main-folder row (or /hub folder <absolute path>) opens the system folder chooser; type a path in the same block when no chooser is available. Then:

  • Two records move together, or nothing does:

    • ~/.dsh/storages/dsh_threads.json → tables.projects[<id>].folder: what dsh-threads renders and what this panel reads directly (no second copy of the truth here);
    • ~/.dsh/storages/workspace.json → tables.workspaces[<workspaceId>].path: a new session's directory is read from here. Writing only the first one would show a new folder while new sessions still opened the old one; so when the second write cannot be made, the whole switch fails and nothing changes.
  • Backup first: each storage file gets a <file>.bak-mainfolder-<timestamp> copy. Writes go through the storage domain dsh-threads / DSH already opened (authoritative memory, serialised write chain); when the host exposes no such service the writer degrades to "re-read → atomic rename" and the panel says this switch wrote the files directly.

  • Validation: the target must exist and be a directory and is canonicalised (realpath, no trailing slash, symlinks resolved). /, /Applications, /System, /Library, /usr and the other system roots are refused, as are the home directory itself, ~/.dsh (and anything under it), ~/.ssh and this plugin's own data directory. A directory another DSH workspace already claims is refused too (DSH's startup consistency check would fail).

  • No silent failure: the writer reads both records back, and on any mismatch or error it rolls both back and shows the reason (including the backup paths) in the panel.

  • What actually changes, honestly: DSH caches workspace records in process memory, therefore

    New sessions and threads use the new folder only once DeepSeek Harness restarts; this conversation stays in its original folder until then.

    The write path never touches a live session's working directory (it only writes those two records), which is exactly why the current conversation does not move. The panel and /hub folder say so; neither claims the switch is immediate.

  • Coupling risk: the dsh_threads / workspace domain names and fields are dsh-threads' and DSH's private contracts. Once upstream PR #61 lands, this should switch to its official entry point. If a field stops matching, the switch fails and rolls back instead of corrupting a record. See docs/folders-feasibility.md.

Three entry points for folders (one component set, one write path)

There are three places to change a folder and they behave the same way: all of them open the same dialog and all of them go through the host half's single write path in src/mainfolder.js (backup → realpath → validate → serialise → read back → roll back). There is no second implementation.

EntryWhereScope
A"Change folder…" plus the "Auxiliary folders" section on the board's current-project cardthe current project only
Ba new "Project folders" section on the settings pageone row at a time, any project or workspace
Ca "⚙ More folders…" button injected into dsh-threads' own "Project settings → General → Folder" cardthe project that card belongs to

All three state the same thing:

Changes are written into dsh-threads' project record and the DSH workspace record; dsh-threads' own settings panel shows them only after a DSH restart (it reads its own client store and does not subscribe to storage changes).

Details:

  • B deliberately has no "change everything": one stray click must never rewrite a dozen project records, so it only edits one row at a time. A project row moves the project record and the workspace record together; a workspace row moves only the workspace record. A workspace a project owns cannot be edited on its own — the request is refused and points at the project row, because both records must move together. A workspace no project uses can be moved alone (workspace.json only, with the same backup / read-back / rollback).
  • C's injection contract: a MutationObserver looks for the .dsht-setting-path anchor inside dsh-threads' folder card; no anchor means no injection at all; repeated triggers are idempotent (one button per card, its copy refreshed with the language); every DOM read and write is inside try/catch, so a changed DOM structure costs the button and never throws into the host or blanks the UI. The card shows that project's folder path, and the button resolves it back to a project record before opening the shared dialog.

The folder dialog (from 0.4.1)

All three entries open the same dialog, and it has exactly these blocks:

Project name (bold)
Current main folder
/Users/me/code/app                       ✕
[Change…]  Type a path                     Saved (2s)
──────────────────────────────────────────────
Auxiliary folders  (2)
  ▱ /Users/me/data              [Remove]
  ▱ /Users/me/notes             [Remove]
  [/Users/me/another____]  [Add]
Auxiliary folders become writable sandbox roots for every session; changes are written to dsh-threads
records, whose settings panel syncs after a restart.
  • The dialog portals into document.body (container #project-hub-dialog-root, role="dialog", aria-modal="true"), so neither the sidebar panel, the settings sheet nor dsh-threads' own modal can sit on top of it: a z-index on a position: fixed node is only ranked inside its own stacking context, and one transform on an ancestor is enough to trap it.
  • Opening locks body scrolling; Esc closes and clicking the scrim closes.
  • The only success feedback is "Saved", which clears itself after 2 seconds — no toast, no alert, no prose.
  • Paths are single-line with an ellipsis; hover shows the full path.
  • The longer explanations (sandbox grants, the restart boundary, why two records must move together) live in the sections below; the dialog keeps one footnote line.

Bilingual (follows the app language)

How to switch to English: sidebar footer → Settings → General → the Language row → pick English (the row comes from DSH's own dsh-client-locale, so the core and other plugins follow too). No reload: this plugin's panel, dialog, settings page and injected button re-render immediately.

Every string the panel, the dialog, the settings page and the injected button show lives in the MESSAGES.zh / MESSAGES.en tables in src/client.js (97 keys each; a test asserts both sides carry exactly the same keys, no empty copy, and no key that nothing shows):

  • The language comes from DSH's locale service (dsh-client-locale): ctx.locale.getLocale() reads the active language, ctx.on("locale/change") follows a switch, and ctx.locale.register("project-hub", { zh, en }) registers the dictionaries. Switching the language re-renders the panel, dialog and settings page immediately — no reload.
  • Missing-key fallback order: active language → English → Chinese → the key itself. English is the backstop, so an untranslated key degrades to English instead of showing board.section.others.
  • Text rendered by the host (the sidebar tab label) is supplied as a thunk, so it follows the next host render.

Install

Requires DeepSeek Harness 0.2.1-rc.2 through 0.3.0.

Desktop app (desktop profile)

Do not use dsh plugin --profile desktop ...: that profile is owned exclusively by the Electron app, and the CLI refuses unconditionally (profile "desktop" is managed exclusively by the Electron application) whether or not the app is running.

Two working paths:

  1. Settings → Plugins → Marketplace, search dsh-claude-project-ui, install, restart.
  2. Manual install (offline, or when handing over a tarball):
mkdir -p ~/.dsh/profiles/desktop/node_modules/dsh-claude-project-ui
tar xzf dsh-claude-project-ui-0.2.0.tgz -C /tmp/pkg
cp -R /tmp/pkg/package/. ~/.dsh/profiles/desktop/node_modules/dsh-claude-project-ui/

Then edit ~/.dsh/profiles/desktop/package.json: add "dsh-claude-project-ui": "^0.2.0" to dependencies and append "dsh-claude-project-ui" to dsh.profile.bundles, then quit DSH completely (⌘Q) and start it again.

Adding the dependency without the dsh.profile.bundles entry does not load the plugin — DSH only mounts plugins from the bundles layer.

Other profiles (web / tui / custom)

Those are started from the CLI, so the plugin manager works normally:

dsh plugin --profile web add dsh-claude-project-ui

Uninstall

Desktop app: remove it from dependencies and dsh.profile.bundles, delete ~/.dsh/profiles/desktop/node_modules/dsh-claude-project-ui, restart. Other profiles: dsh plugin --profile web remove dsh-claude-project-ui.

Data stays in ~/.dsh/project-hub/; uninstalling does not delete it.

Quick start (3 steps)

After installing and quitting DSH completely and starting it again:

/hub status        which project am I in, how much knowledge / how many tasks
/hub note release gate is node test/harness.mjs
/hub add release checklist | 1) run tests 2) npm pack 3) gh release
/hub brief         a project brief to paste into thread_open.task

The "▤ 项目看板" tab in the right pane should now show the task and thread state you just added; tui / headless have no sidebar, so use /hub board there. When you open a new thread it starts with the project brief, the board snapshot and recent progress already attached.

Configuration

Override in the profile's cordis.patch.yml:

- id: dsh-claude-project-ui
  name: "dsh-claude-project-ui"
  config:
    dataDir: ""                      # default ~/.dsh/project-hub
    threadsStorage: ""               # default ~/.dsh/storages/dsh_threads.json
    workspaceStorage: ""             # default: workspace.json next to threadsStorage (written on a folder switch)
    knowledgeIndexMaxChars: 280
    kbIndexMaxDocs: 3
    boardContextMaxChars: 700
    digestContextMaxChars: 700
    maxExtraFolders: 8               # auxiliary folders a project may mount
    foldersContextMaxChars: 600      # cap for the injected mount list
    briefMaxChars: 4000
    maxNotes: 200
    maxDocs: 200
    maxKnowledgeChars: 4000000
    hideResolvedThreads: true        # hide resolved/archived threads in the board and injection
    autoConvergeReports: true        # roll thread reports up into board tasks (idempotent)
FieldDefaultEffect
dataDir~/.dsh/project-hubRoot for knowledge, tasks and notes; pointing it elsewhere gives you a separate set of projects
threadsStorage~/.dsh/storages/dsh_threads.jsonRead-only for detection; also written when the main folder is switched (see above). A format change degrades to "no injection"
workspaceStorageworkspace.json next to threadsStorageWritten only on a folder switch: a new session's directory comes from workspaces[].path here; a wrong value makes the switch fail and roll back
knowledgeIndexMaxChars280Character cap for the injected knowledge index
kbIndexMaxDocs3How many documents the index lists before pointing at kb_search
boardContextMaxChars700Character cap for the injected board snapshot
digestContextMaxChars700Character cap for the injected recent-progress digest
maxExtraFolders8Auxiliary folders a project may mount
foldersContextMaxChars600Character cap for the injected auxiliary-folder list
briefMaxChars4000Cap for one context_brief / /hub brief result
maxNotes200Progress notes kept per project
maxDocs200Knowledge documents allowed per project
maxKnowledgeChars4000000Total knowledge characters allowed per project
hideResolvedThreadstrueInitial value for the ⚙ "show resolved and archived threads"; once set, settings.json wins. board_list all=true always shows everything for one call
autoConvergeReportstrueInitial value for the ⚙ "roll thread reports into tasks" toggle (idempotent by threadId)

Data

~/.dsh/project-hub/settings.json          board settings (language / threads / cards / sort; ours)
~/.dsh/project-hub/projects/<projectId>/
  knowledge.json   knowledge documents
  board.json       manual tasks
  notes.json       project context notes
  folders.json     auxiliary folder mounts (this plugin's own record)

Plain JSON, written atomically (temp file + rename); safe to back up or edit by hand.

A main-folder switch does not touch this directory: it writes ~/.dsh/storages/dsh_threads.json and ~/.dsh/storages/workspace.json, keeping a *.bak-mainfolder-<timestamp> copy of every file it changes.

Known limitations

  • Project detection reads dsh-threads' storage file. If that format changes, detection breaks and the plugin silently degrades to "no injection" rather than erroring.
  • Retrieval is lexical (CJK bigrams + English words + term-frequency normalisation): no vector search and no LLM summarisation, so write clear titles and keywords.
  • Summaries are not model-generated: the automatic part comes from dsh-threads' lastReport, the manual part from hub_note. Nothing the main conversation never reported will show up.
  • Injection is truncated by characters (700–900 per section by default), not by tokens.
  • The panel is read-only apart from adding/removing auxiliary folders and switching the main folder: creating, changing or deleting tasks today means board_add / board_update / /hub task|done|rm.
  • Switching the main folder depends on the private fields of two storage domains (dsh_threads and workspace). Once upstream PR #61 lands this should move to its entry point; if a field stops matching, the switch errors out and rolls back rather than corrupting a record.
  • Switching the main folder does not move the current conversation: only sessions and threads created after a DSH restart use the new directory, and the panel plus /hub folder say exactly that.
  • Auxiliary folder grants only take effect under workspace-write; read-only grants nothing. Grants are runtime state that must be re-registered after a restart / resume (the sweep does it, so it can lag up to 10 seconds).
  • Refreshes are polled: every 10 seconds plus on agent status changes, so a snapshot can be up to 10 seconds stale.
  • The board hides resolved/archived threads by default (the ⚙ popover can show them); board_list all=true or /hub board --all shows everything for one call.
  • The ⚙ "Manage project folders…" does not jump into the settings page: DSH exposes no client API to open a specific settings section, so it renders the same manager component inside the popover instead (one row at a time, no bulk action).
  • hideResolvedThreads / autoConvergeReports in the config are initial defaults only: once the panel toggle is used, the settings file decides.

Verification record (2026-11-18, local desktop profile)

LayerResultEvidence
CommandsPassSession log command/run + command/done; a 5-line paste and add | body both worked; knowledge.json written
ToolsPassIn the project's main conversation the model called tools.kb_search({query:"release"}) through PTC; returned [k-1] release checklist score=0.343
Injection (knowledge)PassReal system prompt contained the shared-knowledge section
Injection (board/progress)PassThread #2's request body (user/message, 12.7 KB) contained ## 项目看板, two thread rows and ## 项目进展 verbatim; knowledge rode in system/message (section vs context channels)
Schema compatibilityPassnode test/spec-check.mjs validates all 10 tool definitions against the host DSL
LogicPassnode test/harness.mjs, 30 checks (changedFiles, hiding rules, rollup idempotency, /hub doctor, extraFolders persistence / prompt injection / kb_add path boundary / folder route auth, main-folder switch (both records, backup, refused paths, concurrent writes, rollback), /hub folder, the route)

Relationship to Team mode

A Team-mode task board belongs to one session's subagent tree; this plugin's board belongs to one dsh-threads project (main conversation plus all of its threads). They complement each other and never write to the same place.

License

MIT — see LICENSE.

Plugin correlati