How to use deepseek-harness-desktop
Adds multi-column task board to DSH Web GUI with sidebar entry for one-click switching. Tasks execute through Host real session and write back status. Five-segment cron timing is maintained by Host with browser fallback.
This article is auto-derived from indexed fields (wiki / faq / compatibility_json), not freshly AI-generated.
This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.
Quick start
deepseek-harness-desktop
— source: plugin_wiki.wiki_content
Install & verify
dsh plugin --profile web add @linxin666/dsh-client-ui-task-board
Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.
— source: plugins.install
Key points
- 可靠 Windows 启动:移除 PowerShell 5.1
-WindowStyle Hidden与 Electron Node 模式的冲突,隐藏窗口仍由spawn的windowsHide处理;空旧补丁、状态订阅竞态和 IPC 错误不会再把启动页永久留在 8%。 - 验证过的 Runtime 组合:内置
@deepseek-ai/dsh0.1.0-rc.7、dshmarket1.15.0、Web UI 聚合0.2.3、兼容 rc.7 的 Codex Connect 与dsh-live-stats0.1.20,Stable 继续精确锁定而非追随latest。 - 托盘与后台自动化需显式选择:默认关闭仍会退出。选择“最小化到托盘并启用后台自动化”后,关闭主窗口才保留 Runtime 和到期任务;显式退出、更新、安全模式和崩溃路径一律完整停止。
- Host 持久任务调度:Task Board 保存时区、cron 槽位、租约、misfire/running 策略和确定性运行键;启用后台自动化时通过真实 DSH Session 执行并回写 Task Run,Host 不可用时仍回退浏览器调度。
- 可审计的扩展边界:扩展坞校验
dsh.compatibility的版本、Desktop API、能力、Surface 与运行时证据,并在 profile 写入desktop-plugins.lock.json。browser-safe SDK 不导入 Electron 或私有 DSH 模块;预览的外部打开仅传工作区根和相对路径,Host 验证后才交给系统。
— source: plugin_wiki.readme_en (fallback readme_raw)
FAQ
What does this plugin do?
Adds a 'Task Board' entry in the sidebar of the DSH Web interface. After clicking, the middle column switches to a multi-column Kanban board (To Plan/Todo/In Progress/Completed/Failed), providing task creation, execution, status writing-back, and scheduled dispatching.
Does task execution consume API quota?
Yes. Each execution creates a real workspace session through the client runtime and drives the agent with session.prompt, consuming the same API quota as a regular session.
Where is task data stored?
The authoritative v3 ledger is located at Host-side DSH_HOME/profiles/
Does the scheduled task require the board to stay open?
Not required. As a Desktop 2.7 host-job adapter, when the user explicitly enables background automation, the Host claims expiring slots via lease, timezone cron, and deterministic TaskRun; other runtimes (including old Web Host, abnormal state format, or no adapter) fall back to the browser tab's ticker, which requires the tab to remain open.
Will missed cron trigger points be backfilled?
Skipped by default. All missed trigger points from host-side sleep/restart are skipped; explicit run-once can merge and backfill at most one slot, and queue-next retains at most one pending execution slot during task runtime.
Will task data be lost after uninstallation?
No. Uninstall only removes the plugin registration line and restores the GUI to its original state; the ledger file remains in the Host-side state/task-board directory.
What needs to be done after installation?
Need to restart the dsh web process once. Profile layer (bundle line, dsh.client metadata) is only read at process startup; a simple page refresh won't make the entry effective.
What is Worktree review?
Desktop 2.6 tasks can choose shared-workspace or Git Worktree; when Runtime Provider provides workspace/session observation capability, Host creates a controlled Worktree, displays bounded Evidence, and provides Commit/Merge/Keep/Discard; when capability is missing, it explicitly falls back to shared-workspace.
— source: plugin_wiki.faq_json
Compatibility
- DSH: >=0.1.0-rc.7 <0.2.0(package.json#dsh.compatibility.runtime),Desktop 2.7.0-2.x(package.json#dsh.compatibility.desktop)
- Node: 源码未声明 engines;monorepo 约定 ^22.19 || >=24(package.json#devDependencies @types/node ^22.20.0)
— source: plugin_wiki.compatibility_json
Pitfalls
Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.
— source: general rule