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-web-ui-settings

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

What if I can't see this section in the settings page after installation?

You need to restart dsh web for it to appear; the section relies on the official @deepseek-ai/dsh-client-ui-settings to provide the settings.section slot. If the host doesn't have this SDK installed, the section won't be displayed (README.zh.md:47).

Does this plugin require any additional configuration?

By default, it works without any configuration. If you want the reverse proxy on the same host to forward requests, you need to write trustedProxyHosts and proxyTokenEnv (the latter is the environment variable name that holds the token) in the profile, and set an environment variable with the same name.

I'm using rc.7 or higher on the host, do I still need this bridge?

In most cases, no. When the host's apiproxy natively exposes the corresponding namespace, the browser automatically uses the official settings scope, and the bridge provided by this package won't be activated (src/client/compat-settings-scope.ts:230-262).

The card shows 'Not exposed to settings page' - what should I do?

This indicates the current host apiproxy doesn't recognize this namespace. The fallback bridge provided by this package will let the local browser take priority, but it still requires this namespace to be registered in the host settings (allowlist.ts:85-94).

How should I fill in trustedProxyHosts?

It must be a normalized host[:port], such as dsh.example.com or 127.0.0.1:8443. Case and port range are validated during parsing; if invalid, startup will fail (bridge.ts:88-102).

Can I write the reverse proxy token in plain text in the profile?

No. The profile only allows writing proxyTokenEnv (the environment variable name), not the actual token. The token is read from the process environment variables to prevent leakage to the configuration repository (README.zh.md:43 / src/index.ts:36-39).

Are the entries in the 'Community Plugins' card safe?

This card is just a link list; index entries are registered by contributors themselves, and this package doesn't include or bundle any third-party code. Please assess the author and repository yourself before installation (locales.ts:39-41).

How do I uninstall it?

Just use dsh plugin --profile web remove to uninstall. This plugin doesn't write to local storage or create resources outside the host, so there will be no residual data after uninstallation.

— source: plugin_wiki.faq_json

Compatibility

• DSH: >=0.1.0-rc.7（package.json devDependencies 中 @deepseek-ai/dsh-* 系列均要求 ^0.1.0-rc.7）
• Node: ^22.19 || >=24（据 packages/AGENTS.md:9；本包 package.json 未声明 engines）

— 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