Everything is a Setup.
Discover, understand, install, update, repair, and compose the DeepSeek Harness ecosystem from one desktop-native control center.
Important
This is an independent community distribution and ecosystem project. DeepSeek Harness itself is developed in the upstream deepseek-ai/deepseek-harness repository.
| Layer | What users see | What it does |
|---|---|---|
| HUB application | A native desktop marketplace and component manager | Aggregates DSHMK, curated sources, GitHub discovery, starred projects, local packages, installed components, updates, repair, and restart workflows |
| Setup registry | Consistent Setup-style installation pages | Describes source identity, license, certificate/signature state, permissions, network use, install evidence, options, rollback, and compatibility before installation |
| HUB distribution | HUB Setup, HUB Runtime, and developer builds | Provides the independent Windows WebView2 host, HUB CONFIG, private Node.js runtime, and offline recovery |
The HUB does not claim that arbitrary GitHub source can safely become an EXE. Online entries are rendered as virtual Setup experiences backed by inspectable recipes. Standalone Setup EXEs belong to the curated library and are accepted only after repeatable installation, launch, update, and uninstall checks.
The current Windows assets are published on the Releases page.
| Asset | Best for | Network requirement |
|---|---|---|
| Full Setup | First-time users and unreliable networks | Can install the bundled Runtime and WebView2 offline |
| Lite Setup | Smaller initial download | Downloads a verified Runtime, or imports a manually downloaded Runtime ZIP |
| Portable ZIP | Evaluation and removable storage | Requires WebView2 already installed |
| Runtime ZIP | Repair, offline transfer, and Lite Setup import | No installer UI by itself |
- Native HUB process — separate taskbar identity, icon, window lifecycle, and restart behavior from the main Desktop application.
- Evidence-rich details — source, release/ref, license, certificate state, validation result, install guide, permissions, dependencies, and expected file changes.
- One-click Setup where possible — deterministic recipes for recognized packages; manual download/import remains available when a network route is unreliable.
- Honest fallbacks — unsupported or ambiguous projects open an assisted Setup flow instead of pretending the install succeeded.
- Local ownership — installed, prepared, offline, starred, and locally-authored packages remain distinct collections.
- Composable editing — generated edit paths and manifests make it practical to hand a component to an AI or developer without mixing it into discovery.
flowchart LR
Sources["DSHMK · Curated · GitHub · Local"] --> Normalize["Catalog normalizer"]
Normalize --> Evidence["Evidence + compatibility model"]
Evidence --> Hub["Native HUB application"]
Registry["Setup Registry v1"] --> Hub
Hub --> Virtual["Virtual Setup renderer"]
Hub --> Standalone["Vetted standalone Setup EXE"]
Virtual --> Runtime["DeepSeek Harness Desktop runtime"]
Standalone --> Runtime
Runtime --> Profiles["Desktop profile · HUB profile"]
Read the full architecture guide and desktop distribution boundary.
.
├─ apps/ DSH command and application entry points
├─ packages/ HUB Web UI, Setup protocol, registry, and shared DSH packages
├─ windows/ Native HUB host, Runtime, Setup builder, and release assembly
├─ registry/ Public first-party Setup catalog and JSON Schema
├─ examples/setup-package/ Minimal authoring example
├─ examples/setup-workspace/ Editable source/build/component workspace example
├─ snapshots/ Full-screen bilingual development snapshots
├─ docs/ Architecture, catalog, release, and package specifications
├─ scripts/ Dependency-free repository validation
└─ .github/ CI, issue forms, pull request policy, and release notes config
The HUB implementation is the root project in this repository. The native host, Runtime, Setup builder, Web UI, Setup protocol, catalog adapters, tests, and all shared DSH packages are directly editable here. See the source map for the exact customization points. deepseek-harness-desktop is a separate Desktop distribution and is not the HUB source or release center.
npm run build:hubThe build entry checks Node.js, pnpm, and WebView2 SDK prerequisites and writes results to the repository-level dist/ directory. Contributors can work directly in the root pnpm workspace and modify the native host, Runtime, Setup builder, or Web UI without crossing into another repository.
- Read the Setup package specification.
- Start from
examples/setup-package/manifest.json. For editable local or AI-assisted builds, also read Custom Setup Workspaces and start fromexamples/setup-workspace/manifest.json. - Run
npm run validatelocally. - Open a Setup submission issue with installation evidence.
- Submit a pull request after the package has stable install and uninstall behavior.
Standalone EXEs additionally require hashes, source identity, privilege declaration, a clean-machine install log, launch evidence, update behavior, and uninstall residue notes.
The project is in an early release-candidate stage. Registry v1 is intentionally conservative: its data model is stable enough for tooling, while catalog contents and desktop UX continue to evolve quickly.
Code and first-party specifications are released under the permissive MIT License. Third-party packages keep their own licenses; catalog inclusion never changes upstream ownership or licensing.