DSH-Shell

DSH Shell

Native desktop shells for the DeepSeek Harness (dsh) web UI — a real window instead of a browser tab, and real ownership of the dsh process behind it.

This repository holds two independent implementations of that idea:

Directory · Platform · Stack · Docs windows/ · Windows 10+ · Rust · Tauri 2 · WebView2 · windows/README.md macos/ · macOS · Swift · SwiftUI · WKWebView · macos/README.md

They share the goal and nothing else. Neither wraps the other, they import no code from each other, and each is built, tested and released on its own — so a directory's own README is the one to read.

They do, however, have to agree about dsh. That agreement is written down rather than left to drift:

Document · What it is docs/dsh-shell-contract.md · The specification both implementations must satisfy: endpoint resolution, the stub-dsh fixture table, the preflight guards, PID ownership, configuration compatibility. Change a rule here and you change both sides, with a test on each. docs/dsh-desktop-contract.md · A measurement of what the dsh Web UI actually does when a desktop host declares itself, against real dsh@0.2.0-rc.2. Screenshots and raw JSON under docs/probe/. Produced by macos/tools/dsh-probe.

It changed the Windows shell's chrome strategy and it is the reason the macOS shell's probe-adoption feature was removed rather than tuned.

Building

Windows (Rust and cargo-tauri):

cd windows\src-tauri
cargo test
cargo tauri build      # -> windows\src-tauri\target\release\bundle\{msi,nsis}

macOS (Xcode and Swift Package Manager): see macos/README.md.

Releases

Git tags share a single namespace across the repository, so each implementation prefixes its version with its platform:

• windows-v0.1.0 — the Tauri shell.
• v0.1.0, v0.1.2, … — the SwiftUI shell, which predates this layout and

keeps its unprefixed tags.

Each release's notes name the implementation, and its installers are attached to that release only.

License

MIT, per implementation — see windows/LICENSE and macos/LICENSE. The two carry different copyright holders, so there is deliberately no single top-level LICENSE.