dsh-result-only-view

English · 简体中文

English

A Results only toggle for DeepSeek Harness conversations — on the dsh web browser surface and in the DeepSeek Harness desktop app. Turn it on and thinking, tool-call and context-injection rows fold away — only your messages and the final replies remain. Open any of them again whenever you want the details.

• Default on; the state persists in localStorage.
• While the agent runs — one compact chip per running step (tool name + args hint, or the latest thinking line). Click a chip to reveal and expand that step's native row mid-run. With no active step, a single live status line shows the latest one.
• After a turn settles — a Processed N steps · Xs ▸ trace appears at the turn tail: click to expand that turn's process rows; click again to fold them back. Moving the mouse across the line does nothing — expansion is strictly click-driven.
• Fold modes — Auto folds settled turns for you; Manual keeps them visible until you fold them from the trace line.
• Never hidden — whitelisted interactive cards (ask_user_question, cordis_run) and composer approval prompts stay visible.
• Settings → General → Results only: show/hide the trace, restore animations under reduced motion, pick the fold mode. zh-CN/en localized.

Install

dsh plugin --profile web add dsh-result-only-view

Then restart dsh web. Uninstall with dsh plugin --profile web remove dsh-result-only-view + restart.

Desktop app — the desktop profile is owned by the application, so use its own plugin manager instead of the standalone CLI: Settings → Plugins → install dsh-result-only-view, then restart the app. The equivalent command line, run through the desktop's bundled CLI, is:

"<install dir>/DeepSeek Harness.exe" --expose-internals \
  "<install dir>/resources/app.asar/dsh/node_modules/@deepseek-ai/dsh-desktop-host/lib/cli.js" \
  plugin --profile desktop add dsh-result-only-view

Notes

• One build covers both surfaces: the desktop host serves the same Web application as dsh web, so the browser half is loaded through the same dsh.client.platform: "web" declaration. It understands both conversation DOM generations in use today (0.1.x and 0.2.0: nested step seats, the preparing tool state, the settled-turn Completed in … controller row, and the turnTail slot's chain/list difference).
• Client-side only: no network requests, no filesystem access, no credentials. Reads/writes localStorage and reads the conversation DOM read-only — the product DOM is never modified.
• Hiding relies on stable product DOM attributes plus a MutationObserver for chips. If a DSH update changes the attributes, the plugin degrades gracefully (rows stop hiding) — please report DSH + plugin versions in an issue.
• Row-level CSS fallbacks cover browsers without :has().

简体中文

DeepSeek Harness 对话界面的「只看结果」开关——dsh web 浏览器界面与 DeepSeek Harness 桌面端通用。开启后思考行、工具调用行与上下文注入行全部折叠——对话里只剩你的消息和最终回复；需要细节时随时点开。

• 默认开启，状态保存在 localStorage。
• Agent 运行中：每个进行中的步骤显示一枚摘要芯片（工具名 + 参数提示，或最新一行思考）。点击芯片可立即展开该步骤的原生行查看参数与输出；没有运行中步骤时显示一条实时状态行。
• 回合结束后：回合尾部出现「已处理 N 步 · Xs ▸」，点击展开该回合的过程行，再次点击收起。鼠标滑过该行不会有任何反应——只有点击才会展开。
• 折叠方式：自动——回合结束后自动折叠过程行；手动——保留过程行，由你点击痕迹行折叠。
• 永不隐藏：白名单交互卡片（ask_user_question、cordis_run）与输入框审批提示始终可见。
• 设置 → 常规 → 只看结果：开关痕迹行、减少动态效果下恢复动画、选择折叠方式。中英双语。

安装

dsh plugin --profile web add dsh-result-only-view

然后重启 dsh web。卸载用 dsh plugin --profile web remove dsh-result-only-view 再重启。

桌面端——desktop 配置由应用自身管理，请用应用内的插件管理器安装：设置 → 插件 → 安装 dsh-result-only-view，然后重启应用。等价的命令行方式（走桌面端自带 CLI）：

"<安装目录>/DeepSeek Harness.exe" --expose-internals \
  "<安装目录>/resources/app.asar/dsh/node_modules/@deepseek-ai/dsh-desktop-host/lib/cli.js" \
  plugin --profile desktop add dsh-result-only-view

说明

• 一套构建同时覆盖两端：桌面端 Host 与 dsh web 提供同一个 Web 应用，浏览器半侧仍以 dsh.client.platform: "web" 声明加载。它同时适配当前两代对话 DOM（0.1.x 与 0.2.0： 嵌套的步骤分组、preparing 工具状态、回合结束后的 Completed in … 控制行，以及 turnTail 槽位 chain/list 的差异）。
• 纯客户端：无网络请求、不访问文件系统、不接触凭据；仅读写 localStorage 并只读对话 DOM，不改产品 DOM 结构。
• 隐藏依赖稳定的产品 DOM 属性并用 MutationObserver 渲染芯片；若产品升级改动属性会优雅降级（停止隐藏），请在 issue 中附上双方版本。
• 对不支持 :has() 的浏览器保留行级 CSS 兜底。

License

MIT — see LICENSE. Security issues: open a GitHub issue titled [security].