Frequently asked questions
Answers about setup, unsigned-build warnings, privacy and updates for DSH Desktop v0.2.17.
What is DSH Desktop?
It is a community desktop packaging of the official DeepSeek Harness. A Tauri 2 shell, a Rust supervisor sidecar, and a bundled Node.js runtime run the unmodified Harness web UI as a native Windows or macOS application.
Do I need to install Node.js or run commands in a terminal?
No. A pinned Node.js runtime is bundled inside the app, and the supervisor starts the Harness automatically. Your system Node installation, if any, is never used.
Is this an official DeepSeek product?
No. It is maintained by the web-casa community. The DeepSeek Harness package itself is official and unmodified; this project only pins it and packages it.
Why does Windows SmartScreen or macOS Gatekeeper warn me?
The GitHub v0.2.17 preview packages are not yet code-signed or notarized. Verify the published SHA-256 checksum, then on Windows choose More info → Run anyway; on macOS right-click the app and choose Open. The Microsoft Store package uses the Store installation flow after publication.
Does the app send telemetry or analytics?
Session telemetry is disabled by default through DSH_TELEMETRY_DISABLED=1. Child-process environment variables such as NODE_OPTIONS and npm_config_* are sanitized before the Harness starts. See the security page for the full posture.
Does the app update itself automatically?
The separately distributed Windows build checks for signed updates and asks before installing one. The Microsoft Store build disables that updater because Store owns package delivery and updates. macOS updates are currently manual.
Which platforms are supported?
Windows 10/11 x64 (NSIS installer) and macOS on Apple Silicon (DMG). Linux is a development target only, not a distribution target.
How is this different from running the DeepSeek Harness CLI myself?
The desktop packaging adds supervised process lifecycle, crash detection and auto-restart, an isolated DSH_HOME data directory, privacy defaults, and a zero-IPC webview boundary. The Harness itself behaves the same.
Is DSH Desktop free?
Yes. The packaging is MIT licensed and free to download and use. The bundled DeepSeek Harness and its npm dependencies retain their own open-source licenses, which are shipped inside the package.
How do I report a security issue?
Use the GitHub Security Advisory flow on the repository (Security tab → Report a vulnerability) for private disclosure, or contact the maintainers by email.
Where is my data stored? Can I back up or migrate it?
Data lives in the platform application-data directory under a harness/ subfolder, isolated from the CLI's ~/.dsh. The in-app diagnostics button shows the exact path. To back up or migrate, close the app completely and copy that directory; do not replace it with a symlink.
How does plugin installation work?
The in-app Cordis marketplace shows entries even when they are blocked, deprecated or incompatible, but those entries cannot produce an install action. Eligible npm packages are rechecked, integrity-verified, installed with build scripts disabled and left pending until you explicitly activate them. The Store build additionally allows only the reviewed cordis.run package list and rejects local sideloading.
What happens if the Harness port is occupied?
Nothing you need to handle. The app starts the Harness with --port 0 on 127.0.0.1, so the operating system assigns a free random port at launch.
How do I completely uninstall?
Windows: uninstall normally, then delete the app-data harness/ folder. macOS: drag the app to the Trash, then delete ~/Library/Application Support/com.yeagoo.dsh-desktop/harness. The diagnostics panel shows the exact data path on your machine.
Does it run on Intel Macs or Windows ARM?
GitHub Releases currently ship Windows x64 and macOS Apple Silicon packages. The Microsoft Store submission also includes a native Windows arm64 MSIX package; it becomes available only after Store certification and publication. Intel Mac is not distributed.
The app crashed or keeps restarting. What should I check?
Use the in-app diagnostics button to copy a JSON snapshot, then include it in a GitHub issue. By design, the supervisor restarts the Harness after roughly 40 seconds of no heartbeat, so repeated restarts usually mean the Harness event loop is blocked.