DeepSeek Harness Desktop v0.1.16

What changed

• Pinned the upstream runtime to @deepseek-ai/dsh@0.2.1-rc.2.
• DSH 0.2.1 makes plugin version compatibility prefer a plugin's engines.dsh range and otherwise fall back to its @deepseek-ai/dsh-* peers. Because a ^0.1.x peer range no longer covers the 0.2 line, webview-compat and webview-links now declare @deepseek-ai/dsh-host-webserver: ^0.1.5-rc.1 || ^0.2.0-rc.2 and move to 0.1.1, so they stay accepted by the runtime's compatibility preflight. The other preinstalled plugins declare no DSH peers and were already accepted.
• Rebuilt the plugin sources against 0.2.1-rc.2: tsc --noEmit is clean and the production bundles build. diff-review's 0.2.1 bundle is byte-for-byte identical to its 0.1.7 build, so its behavior is unchanged.
• Everything else is unchanged from v0.1.15: open-editor, diff-review (git working-tree review: staged/unstaged, accept/revert, commit/push/PR, AI review), account-login, webview-compat (the Iterator shim for older WebKit), webview-links (external links to the system browser), trusted-LAN phone remote and desktop notifications.

Verification

An isolated end-to-end run of @deepseek-ai/dsh@0.2.1-rc.2 with the shipped preinstall set reaches ready and loads the Web UI with no plugin console errors. The desktop shell builds, and its Go test suite passes.

Compatibility

Upstream DSH	@deepseek-ai/dsh@0.2.1-rc.2
Node.js	22.19+ on the 22.x line, or 24.2+ on the 24.x line
Desktop platforms	macOS universal, Windows amd64, Linux amd64

Downloads

• macOS universal DMG
• macOS universal ZIP
• Windows amd64 EXE
• Linux amd64 tar.gz

Known limitations

• The first launch downloads the 0.2.1 dependency set, which is larger than earlier lines; on a slow connection the 3-minute readiness window can expire, so let the download finish and relaunch.
• diff-review reviews the git working tree, not in-conversation session changes; use the upstream changed-files card for those.
• Phone access is for a trusted LAN, not a public internet relay. The host uses HTTPS and device pairing; do not expose it directly to the internet.
• Node.js and npm must be installed separately.
• Windows executables are not code-signed; macOS packages are signed with a Developer ID certificate and notarized.
• Upstream DeepSeek Harness remains in developer preview and may introduce compatibility-breaking changes.