dsh-workflow-map: 把会话折叠成一张分步工作流地图

[Joz739]

非官方插件 —— 社区成员独立开发与维护，未经 DeepSeek 官方审核或推荐。

Unofficial plugin — built and maintained by a community member. Not a DeepSeek product, and not reviewed or endorsed by DeepSeek.

dsh-workflow-map：把会话折叠成一张分步工作流地图

长任务的会话翻起来很累。上千条事件里想知道现在走到哪一步、这一步在干什么、还剩多少，只能往上翻。

这个插件把会话折叠成一屏：每步一张卡片串成一条主流程，卡片两侧挂这一步碰过的工具和文件类型，点一下展开分步详情。侧边栏、主内容区、会话标签栏三个入口读同一份数据，步数不会互相打架。

• 项目：https://github.com/Joz739/dsh-workflow-map
• npm：https://www.npmjs.com/package/dsh-workflow-map
• 安装：dsh plugin --profile desktop add dsh-workflow-map

关于进度数字

会话里的"进度"有三个来源，它们经常互相矛盾：待办表是模型随手写的，stepProgress/report 是模型自报的，计划文件（PAE）写一次就永远留在 .pae/ 里。三者对不上时，"已完成 75%"就只是个说法。

所以这个插件不追求一个好看的百分比，而是给每个数字标注它是从哪来的——待办表数出来的、模型自报的、还是按时间基线推的。四个来源都用不上时它不显示数字，而不是补一个 0 或 100；没结束的步也不会显示 100%。

几个界面

分步详情：这一步的类型清单、调用参数与结果摘要	热注入：提示词排进下一步队列，被取用前可撤回

安装要求

DSH >=0.2.1-rc.1 <0.3.0-0，Node >=20。

插件不联网，不起子进程，不写系统目录，package.json 里没有 dependencies。唯一的磁盘读取是 .pae/ 下的计划文件，只读，目录不在就跳过。热注入需要一个正在运行的会话——空闲会话返回 409，它不会替你排队。

验证到什么程度

DSH 0.2.1-rc.5 + Windows + Web 界面上实际用过。

0.2.1-rc.1 到 rc.4 只做了静态契约核验——读宿主包的元数据和契约锚点，没有真机启动过。方法、逐版本证据与已知差异在 docs/host-compatibility.md。

没测过的是 macOS、Linux、Client 界面和 CLI 界面。哪个版本、哪个平台上出了问题是正常的，回复我。

已知限制

• 0.3.0 及以后的内核不支持，engines.dsh 的上界是 <0.3.0-0。
• 单步最多画 300 个节点、整个会话最多 1200 个；超出部分会计数并在界面上写明"已省略 N 个"，不会静默丢掉。
• 上面几张图是离屏渲染的虚构任务，不是真实会话录屏。

反馈

有问题开 Issue，或者直接回复本帖，说一下你的 DSH 版本和操作系统。

---

English

Long sessions are hard to read back. In a conversation with a thousand events, finding out which step you are on, what that step is doing, and how much is left means scrolling up.

This plugin folds a session into one screen: a card per step in a single flow, each card flanked by the tools and file types that step touched, and a click opens the step's detail. The sidebar, the main area and the conversation tab strip all read the same data, so their step counts cannot disagree.

• Project: https://github.com/Joz739/dsh-workflow-map
• npm: https://www.npmjs.com/package/dsh-workflow-map
• Install: dsh plugin --profile desktop add dsh-workflow-map

About the percentage

A session has three competing sources for "progress": the todo list the model writes, the stepProgress/report events the model reports, and a plan file (PAE) that is written once and then stays in .pae/ forever. When they disagree, "75% complete" is just a claim.

So the plugin does not aim for a nice-looking number. It labels where each number came from — counted from the todo list, reported by the model, or derived from a time baseline — and when none of the four sources applies it shows no number rather than inventing a 0 or a 100. A step that has not finished never shows 100%.

Requirements

DSH >=0.2.1-rc.1 <0.3.0-0, Node >=20.

No network calls, no subprocesses, no writes outside the session, and no dependencies in package.json. The only disk read is the plan file under .pae/: read-only, skipped when absent. Hot injection needs a session that is currently running — an idle session answers 409 rather than queueing the message for you.

What has actually been tested

Used on DSH 0.2.1-rc.5, Windows, Web UI.

Versions 0.2.1-rc.1 through rc.4 were checked statically only — reading the host package's metadata and contract anchors, never started on a real host. Method, per-version evidence and known differences are in docs/host-compatibility.md.

Not tested: macOS, Linux, the Client UI, the CLI. Expect trouble on an untested combination; tell me and I will look.

Known limits

• Kernels 0.3.0 and later are not supported; the upper bound of engines.dsh is <0.3.0-0.
• At most 300 nodes per step and 1200 per session are drawn; the rest is counted and shown as "N omitted" in the UI rather than dropped silently.
• The screenshots above are offscreen renders of a fictional task, not a recording of a real session.

Feedback

Open an issue, or just reply here with your DSH version and OS.