Skip to main content

How to use deepseek-harness-desktop

Give DSH Web GUI a Minecraft main menu-style pixel block appearance: a slowly rotating procedural panoramic skybox behind it, gray cobblestone buttons, and wood sign input boxes with corner brackets. Fully offline with no model requests.

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 --allow-build=@linxin666/dsh-client-ui-skin-minecraft github:ningbainb/deepseek-harness-desktop#path:packages/skins/minecraft

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/dsh 0.1.0-rc.7、dshmarket 1.15.0、Web UI 聚合 0.2.3、兼容 rc.7 的 Codex Connect 与 dsh-live-stats 0.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

Does this skin require internet connection? Will it call any models?

No, it doesn't require internet and doesn't call any models. The entire skybox is drawn row by row in SVG by JavaScript locally, including blocks, clouds, mountains, trees, and houses. There are no external textures or network requests. The README and source code comments explicitly state "does not trigger any model requests".

What to do if the skin doesn't take effect after installation?

Installation only puts the skin package into the profile. You also need to execute dsh-skin use minecraft (a helper script in the repository) to mark it as the "currently activated skin". Only one skin can be activated at a time; skins that are not activated will not be enabled.

Will it save my chat records or personal information?

No. The skin package only reads and writes to the DOM (body attributes, a few injected divs, document.title). There is no local storage, network reporting, or backend calls. When uninstalled, the effect cleaner removes each item one by one.

How to switch back to the default appearance?

Use dsh-skin use <other skin name> to switch to another skin, or dsh-skin use none to return to the no-skin state. When the skin package is uninstalled, it will also automatically restore all the body attributes, injected divs, and document title that were written.

Will this package conflict with other skins?

The dsh-skin tool handles mutual exclusion—in the profile's cordis.patch.yml, only one skin line is enabled at a time. Other skins will have disabled: true. So you cannot stack multiple skins at the same time.

What is the difference from official features?

This is just a visual skin. It doesn't inject services, send cordis events, or intercept model requests. All official features (chat, files, settings, plugin marketplace, etc.) work exactly as before. Only buttons, input boxes, and panels are transformed into block/slate/wooden board styles.

Will it leave garbage after uninstallation?

No. The cordis uninstallation process executes the effect cleaner: removes the data-dsh-minecraft body attribute, removes injected stage/scrim, restores the original document title. The unit test tests/apply.spec.ts explicitly covers these cleanup paths.

— source: plugin_wiki.faq_json

Compatibility

  • DSH: 未声明
  • Node: ^22.19.0 || >=24.0.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