dsh-self Usage & Publishing Guide
Operational reference for DeepSeek Harness (dsh@0.2.2-rc.5) users, plugin maintainers, and standalone desktop app authors.
1. Quick Start & Isolated Demo
Prerequisites: Node.js >= 24.9 (baseline 26.12.1), pnpm 11.28.5, and official DeepSeek Harness 0.2.2-rc.5.
npm run build node scripts/launch-official-dsh-demo.mjs
The demo launcher installs the self-contained dsh-self-studio bundle into an isolated profile under .dev/official-dsh-demo/dsh-home and serves official dsh web on http://127.0.0.1:14567 without touching your personal ~/.dsh directory.
2. 6-Step Studio Workbench
- Step 1 · Requirements: Expand short briefs via your
dshdefault model (with deterministic offline fallback), attach reference images (workbench layout vs. workspace content), fetch reference URLs behind the SSRF guard, or import an existingproduct.json. - Step 2 · Blueprints: Pick from Lite, Standard, or Pro blueprints with instant 1:1 light/dark desktop window previews.
- Step 3 · Plugins: Enforces 4-step static admission (
dsh.bundle.patch& no!!js, platform/Node/--ignore-scriptsnative policy,cordis&reactpeers, 3-state compatibility) and 6-dimension conflict filtering while highlighting locally installed DSH plugins. - Step 4 · Appearance: Customize 4 closed-set layouts (
single-column,list-detail,three-pane,dashboard-grid), icons, 8 light/dark color seeds, and home module order. - Step 5 · Preview & Tweak: Isolated child-process preview with desktop/narrow toggles, live conversational natural-language refinement, and instant revision rollback.
- Step 6 · Build & Release: Build native Windows x64 NSIS
.exeinstallers or generate cross-platform recipes (portable transfer bundle, GitHub Actions workflow, Docker/remote script) with persisted release history.
3. DSH Plugin Release Preparation (10 Gates)
Because the monorepo source package uses workspace:*, always use the release script to stage a self-contained artifact and verify all 10 release gates before publishing:
# 1. Pack & run all 10 DSH plugin release gates node scripts/prepare-plugin-release.mjs --pack # 2. Local smoke install into official dsh@0.2.2-rc.5 dsh plugin --profile web add .dev/plugin-release/dsh-self-studio-0.1.0.tgz # 3. Publish to npm from the verified standalone directory only npm publish .dev/plugin-release/dsh-self-studio --access public # 4. Sync a clean standalone public Git dist repo (for github:, dsh.pub & dsh.so) node scripts/prepare-plugin-release.mjs --sync-dist ../dsh-self-studio
This website also hosts a valid format: 1 DSH Custom Plugin Index at https://dsh-self.octoooo.com/dsh/index.json alongside dsh/icons/dsh-self-studio.svg, ready for the official DSH Discover tab as soon as npm publication completes.
4. Standalone CLI Builder
tools/builder acts as an independent trust root that snapshots product.json and platform locks once and runs the 3-step prepackaged pipeline headlessly:
npm run build npm run assemble:base-shell node tools/builder/dist/cli.js \ --product fixtures/qinghe-bids/product.json \ --lock fixtures/qinghe-bids/locks/plugins.win32-x64.lock.json \ --target win32-x64 \ --base-shell .dev/base-shell/win32-x64 \ --out .dev/out/qinghe-bids
To execute the real 5-installer Windows E2E suite (coexistence, same-name disambiguation, rename upgrade, dual-slot switch, downgrade block, and unilateral uninstall), run node scripts/verify-win-e2e.mjs.
5. product.json Contract
The single cross-platform product contract uses strict Zod schemas (zero arbitrary layout trees, script expressions, or raw HTML/CSS) separating frozen identity from mutable brand / theme / home:
| Field | Mutability | Constraints & purpose |
|---|---|---|
identity.* |
Frozen at creation | productId, internalSlug (<= 21 chars), appId, appUserModelId, nsisGuid, executableName, userDataDirName; isolates registry keys, install dirs, and user data. |
brand |
Mutable across revisions | Bilingual displayName (<= 64 chars, control-char stripped), iconSha256, preset or custom icon; rename upgrades clean stale .lnk shortcuts. |
theme.seeds |
Mutable across revisions | 8 light & 8 dark #RRGGBB semantic seeds deterministically deriving 110+ --dsw-* CSS variables and Electron chrome colors with WCAG 4.5:1 clamping. |
home & requiredActions |
Mutable across revisions | Closed-set 4 layout presets, 9 widgets, and 13 standard actions (panel-open, host-service, seeded-session). |
6. Privacy Defaults, Dual-Slot Self-Healing & Diagnostics
- Zero default telemetry: Seed
cordis.patch.ymldisablessession-log-deepseekandplugin-package-inventory-deepseek; host launch enforcesDSH_TELEMETRY_DISABLED=1. - Minimal env whitelist: Host and builder child processes strip
NODE_OPTIONSand external model keys while preserving OS basics, corporate proxies, andSSL_CERT_FILE/NODE_EXTRA_CA_CERTS. - Dual-slot self-healing: Updates switch
<userData>/h/profiles/p-<seedHash>slots atomically and roll back to the previous verified slot after 2 consecutive boot failures. - Redacted diagnostics: Verifies non-symlink files before zipping, redacts API keys, Bearer tokens, JWTs, PEM keys, and local usernames, and physically excludes
.credentials.yamland.env*.
7. Licensing & Commercial Use (Personal & ≤ 20 Internal Users Free)
dsh-self and the original desktop shell runtime & built-in adapters embedded inside generated installers are dual-licensed under PolyForm Noncommercial License 1.0.0 + Small Internal Team Grant (≤ 20 users) + OctoLab Commercial License:
| Scenario | Cost | Terms |
|---|---|---|
| Personal use / free sharing / academic & nonprofits | Free | Covered by PolyForm Noncommercial License 1.0.0; keep LICENSE, COMMERCIAL-LICENSE.md, and THIRD_PARTY_NOTICES.md when sharing. |
| Internal company use (≤ 20 total users) | Free, no license needed | Strictly internal use within the company and affiliates up to 20 total users; not sold or billed to external clients. |
| Internal company use exceeding 20 users (> 20) | Commercial license | Contact octoooo@octoooo.com for organization-wide internal licensing. |
| Selling packaged clients / paid delivery / white-labeling | Commercial license | Regardless of team size, selling, subscribing, agency/client delivery, or white-labeling packaged clients requires a prior commercial license via octoooo@octoooo.com (see COMMERCIAL-LICENSE.md). |
Third-party community plugins: If you bundle third-party community DSH plugins (such as dsh-plugin-bidkit or dsh-design-studio) into a generated client, you must also comply with each plugin author's own license.