starsqvq/deepseek-harness-desktop
Independent Windows desktop packaging for DeepSeek Harness
Gives Windows users a self-contained DeepSeek Harness desktop build. You extract the ZIP as a whole, keep the EXE beside the app directory and double-click it: the app brings its own Node runtime and harness backend, binds a free loopback port instead of requiring an existing local service, and opens the harness UI in a desktop window. The README also documents the build path and the reason v0.1.1 is a source-only release.
Install
⚠️ Install command not yet confirmed — check the README on GitHub for the exact command.
Compatibility
README: independent Windows desktop packaging for the DeepSeek Harness UI. The app ships its own Node runtime and harness backend, starts on an available local loopback port, and does not depend on an existing 127.0.0.1:3080 service. The launcher is intentionally small and starts the unpacked Electron app directory directly to avoid the long CPU-heavy extraction step of a single-file Electron portable executable.
Details
- Repo: starsqvq/deepseek-harness-desktop
- Category: Infrastructure & Deployment
- Stars: 3
- Version: Windows release v0.1.0 (asset verified 2026-09-17; repo 2★, MIT, last push 2026-09-10)
- Last push: 2026-09-10
- First seen: 2026-08-13
Recent updates
The README documents the release layout and the build requirements rather than a release-by-release table; the latest asset-bearing release when checked on 2026-09-17 was v0.1.0.
FAQ
- How do I install it?
- Per the README, download deepseek-harness-desktop-v0.1.0-win-x64.zip from the v0.1.0 release, extract the ZIP as a whole, keep deepseek-harness.exe beside the deepseek-harness-app directory and double-click the EXE.
- Why does v0.1.1 ship no installer?
- The README says v0.1.1 is source-only: it carries the --no-open desktop-shell fix and recovery notes, but the build inputs and the original harness checkout were no longer present on the build machine, so no ZIP was rebuilt.
- Does it need a running dsh service?
- No — the README says the app ships its own Node runtime and harness backend and starts on an available local loopback port, independent of an existing 127.0.0.1:3080 service.