DSH Desktop: no installer for Intel macOS or Linux
DeepSeek Harness Desktop App: a local AI desktop workspace for DSH Sessions, projects, files, web research, plugins, and Office artifacts.
At a glance
- What is it?
- A community-maintained Electron distribution that runs DeepSeek's own Harness runtime and web app inside one Profile, with sixteen bundles pre-installed and a plugin market that reads the official settings slot. The documentation followed here is the Chinese README, and the tree carries an English one beside it. The platform table is short, and the row for Intel macOS and Linux reads: run it from source.
- Who is it for?
- DSH Desktop is careful in the places most distributions are not. The official Profile is the single source of truth, updates pre-check it read-only and never restore what you removed, and two of the sixteen bundled services are openly marked as having no uninstall path.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- vibeinging/dsh-desktop497 ★ · -88
| Repository | 2026-09-11 | 2026-11-21 |
|---|---|---|
| vibeinging/dsh-desktop | 585 | 497 |
-88 Stars in the last 71 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The download table has a row that says source only
Three platforms are listed and one of them is not really supported:
| Platform | Method | Status | | --- | --- | --- | | macOS Apple Silicon | download the `.dmg`, drag into Applications | Developer ID signed and notarized | | Windows x64 | download the `.exe`, choose install scope and client directory | artifacts per the current release page | | macOS Intel / Linux | no official installer | can be run from source |
So the signing and notarization story exists only for one architecture. Windows has a real installer with a scope choice, and its artifacts are whatever the release page currently carries. Everything else is a source checkout.
The install layout is worth knowing before you move things around. The client install directory holds only the application; the Profile, plugins, Session and other DSH data are managed in a separate data directory, and moving the client install location neither migrates nor deletes that data. So an uninstall leaves your work in place, and a reinstall finds it.
A pinned remote plugin with a third-party relay and an unfinished review
The first default bundle is phone remote, pinned to exactly `[email protected]`, shipped alongside a DSH `0.1.5-rc.1` trial line. Its network model is the interesting part: the Host only makes outbound connections and opens no public listening port, and the remote side tries LAN, P2P, TURN and relay in that order, with every path carrying traffic encrypted with Noise IK.
The service behind it is not the project's own. Account, device directory, signaling and relay are provided by a third party at `dsh.r2049.cn`, and device identity and credentials are kept in `DSH_HOME`. Access to the machine is gated through a fixed Harness API allowlist, so the agent still runs tools at its existing permissions, and the page is explicit that direct shell, PTY and general file RPC are not exposed.
What is unfinished is stated rather than glossed. There is no supported self-hosted server, an independent password security review is not complete, real two-machine cross-network testing and long-term stability verification are not done, and the page suggests uninstalling it if you do not need remote access:
dsh plugin --profile web remove ds-harness-remoteThe distribution applies a SHA-256 checksummed compatible projection of the pinned tarball without modifying the official DSH or upstream sources.
Updates pre-check the Profile and never put back what you removed
The update path is the clearest statement of the project's philosophy. Formal installers prompt through a button in the top right corner, hovering shows the changelog, and only after you click does the app download anything, pre-check the Profile, and install. If the Profile or the client errors, you land on a recovery page rather than a reset.
The rationale table states the same guarantees as design commitments. Startup does not overwrite configuration: an existing Profile keeps the user's choices, and on failure the original Profile is preserved and the recovery page opens. Application updates do not change plugins: the Profile is pre-checked read-only before an update, and bundles the user has disabled or uninstalled are not restored.
One caveat is stated in the same spirit. An existing Profile receives the default remote bundle once after an upgrade, but once you disable or uninstall it, later application updates will not bring it back. That is the one case where the app adds something to a Profile you already had, and it says so.
Sixteen default bundles, and two with no uninstall path
A new Profile ships with sixteen bundles, listed in a table with five columns: bundle, type, declared permissions, official management method, and source. The named defaults in the prose include the Better Sidebar workbench, dshmarket, a task board, attachment input, Git Worktree, phone remote, session window teams, and capabilities for projects, Canvas, Office, structured results and model inheritance.
Two rows are typed `desktop-adapter` and their management column says they are desktop base services with no uninstall offered. They declare the widest permissions in the table: parent IPC, browser workspace host, file dialog host and window host for one, and profile filesystem, a controlled pnpm runtime and the CLI runtime for the other. Those are the capabilities the rationale table justifies as native surface exposed only through limited Session-bound methods, and they are also the two pieces you cannot take back out.
Everything else in the list is described as disable-able or uninstall-able, and the bundles marked as local come from `packages/` inside the repository rather than from a registry.
Node 24, routed through a wrapper on every script
The manifest declares `node >=24` in its engines field, and the root carries both a `.node-version` and an `.nvmrc`. What is unusual is that no script invokes node directly. Every entry goes through one wrapper:
"postinstall": "node scripts/run-with-project-node.mjs node scripts/bootstrap.mjs",
"setup": "node scripts/run-with-project-node.mjs node scripts/bootstrap.mjs --force",
"doctor": "node scripts/run-with-project-node.mjs node scripts/doctor.mjs"So the project decides which Node runs its own tooling rather than trusting whatever is on the PATH, which is what makes a pinned `.node-version` meaningful for scripts as well as for people.
The release tooling follows the same shape and is where the platform table reappears. There is a `release:check` family taking a scope of all, macos or windows, static variants, and `release:verify` variants per architecture pointing at `release/mac-arm64/DSH Desktop.app`, `release/mac/DSH Desktop.app` and the Windows path. An arm64 and an Intel macOS verification step coexist even though only one of those ships an installer.
Electron is a host, and the unit of extension is a bundle
The page is explicit that Electron is a thin desktop host: the Agent, the sessions and the plugin system belong to DSH, and the project's own features are split into bundles so that a portable plugin can install into a compatible official Web and into DSH Desktop alike. Only desktop-specific capabilities use an explicit `desktop-adapter` contract, and plugins needing windows, native file dialogs or a browser workspace are expected to declare that and to report their absence on other hosts.
The plugin market reuses the official settings slot rather than replacing the settings page, and it does not create a second plugin database. It shows source, version, compatibility and permissions, with the warning that appearing in the market does not mean the project has reviewed a plugin or bundles it by default.
The CLI operates on that same Profile, and its flags encode the project's position:
dsh plugin --profile web add -w <package>@<exact-version> --save-exact --ignore-scripts
dsh plugin --profile web remove <package>An exact version, saved exactly, with lifecycle scripts disabled.
Three READMEs, a legal directory and a version line that outran its tag
The root holds three README files: the Chinese one this documentation follows, an English one linked from the language switch, and an animated variant. Alongside them sit `PRIVACY.md`, `SECURITY.md`, `THIRD_PARTY_NOTICES.md`, `RELEASE.md` and a `legal/` directory, then `docs/`, `electron/`, `eval/`, `packages/`, `scripts/`, `server/` and `stats/`. The third-party notices file is not decoration here, because one optional plugin is a community skin centre whose assets carry their own upstream licences, some of them CC BY-NC-SA or containing character copyright, which is why it is not bundled by default and left to the user's choice.
The credentials position is stated too: model credentials are managed by DSH settings and the local environment, and the project does not write API keys into its README, its screenshots or its plugin manifests.
The version picture is the loose end. The three newest releases are v0.2.3, v0.2.4 and v0.2.5, with v0.2.5 titled as an updater fix, all inside four days in mid-September. The default branch is `dev` and it was last pushed on 2026-09-30, which is after the newest tag, so the published build and the branch head are different snapshots.
Editorial conclusion
DSH Desktop is careful in the places most distributions are not. The official Profile is the single source of truth, updates pre-check it read-only and never restore what you removed, and two of the sixteen bundled services are openly marked as having no uninstall path. It suits someone who wants DeepSeek's own runtime with a real file tree, Git and terminal instead of a web page, and it does not suit anyone who needs a Linux or Intel macOS binary, or who wants the phone remote feature to be independently audited, since that plugin talks to a third-party service and its own documentation says the password review and cross-network testing are unfinished. Read the platform table before you plan a rollout, and read what a bundle declares before you install one.
Frequently asked questions
Which platforms does DSH Desktop ship an installer for?
macOS Apple Silicon gets a .dmg that is Developer ID signed and notarized, and Windows x64 gets an .exe with an install scope choice. macOS Intel and Linux have no official installer and are run from source. The client directory holds only the application; the Profile, plugins and Session data live in a separate data directory.
What does the bundled phone remote plugin do, and how do I remove it?
It lets a phone, a remote web page or another desktop continue the same Workspace and Session over outbound-only connections, trying LAN, P2P, TURN and relay with Noise IK encrypted traffic. Account, signaling and relay come from a third party at dsh.r2049.cn, no self-hosted server is supported, and removal is dsh plugin --profile web remove ds-harness-remote.
Will a DSH Desktop update bring back a plugin I uninstalled?
No. Updates pre-check the Profile read-only, and bundles the user has disabled or uninstalled are not restored. The one exception is the default remote bundle, which is added once to an existing Profile after an upgrade, and once you disable or uninstall it, later updates leave it alone.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/vibeinging-dsh-desktop)Star history chart for your README
[](https://hysenlabs.com/projects/vibeinging-dsh-desktop)Was this useful?