FAQ / DEEPSEEK HARNESS
DSH Desktop FAQ
Answers about installation, platform support, data isolation, and first-launch questions for the DeepSeek Harness desktop shell.
Is DSH Desktop an official DeepSeek product?
No. It is an independently maintained community desktop shell with no affiliation, authorization, or partnership with DeepSeek AI. The upstream Harness package and trademarks remain subject to their own terms.
Do I need Node.js or a terminal?
Release builds include a pinned Node.js runtime and the Harness dependency closure. End users do not need to install Node.js or run npx @deepseek-ai/dsh web first.
Does the desktop share CLI configuration?
Not by default. The desktop uses ~/.dsh-desktop, while the CLI commonly uses ~/.dsh. Set DSH_HOME=~/.dsh only when you intentionally want to share data.
What if macOS says the developer cannot be verified?
Current macOS builds may not be notarized. Verify the installer source and checksum, then right-click the app in Finder and choose Open. Do not run commands from an untrusted download page.
What if Windows SmartScreen blocks the installer?
Preview builds may not have a commercial code-signing certificate. Verify the source and checksum first; if you trust the build, choose More info → Run anyway.
Which Linux systems are supported?
The current amd64 Debian package targets Debian, Ubuntu, UOS, Deepin, and Kylin-style desktop systems. Dependencies can vary by distribution.
How do I verify an installer?
Use the matching .sha256 file with shasum -a 256 -c filename.sha256 on macOS/Linux or CertUtil -hashfile filename SHA256 on Windows.
What if GitHub is slow?
Use the GitCode mirror listed on the download page. Mirror availability follows release synchronization; fall back to GitHub if a file is missing.
How do I get an API key?
Create one at the DeepSeek Open Platform, then paste it into the model/provider settings in dsh-desktop. API usage is metered.