DSH HUB
HomePlugin StorePlugin PacksCommunityRankingsResourcesPublish Guide
Plugin source
Back to catalog

fellow99 /

fellow99/dsh-desktop-ark

Topic repository only

The official DeepSeek Harness (DSH) Web UI, unmodified, running on HarmonyOS 2in1 / tablet inside the system ArkWeb — with the dsh Host on a real Node.js runtime embedded in the same process. No Electron, no bundled Chromium, no ArkUI rewrite of the Web UI.

★ 5 Stars2 Forks0 IssuesN/A Community rating0 Confirmed installs
View on GitHubProject homepage
READMESource: main@d459e904

中文 | English

DSH Desktop · HarmonyOS Edition

The official DeepSeek Harness (dsh) Web UI, unmodified, running on HarmonyOS 2in1 / tablet inside the system ArkWeb — with the dsh Host on a real Node.js runtime embedded in the same process. No Electron, no bundled Chromium, no ArkUI rewrite.

Version dsh version HarmonyOS API 24 Node 24.2.0 MIT

What you get

  • The same dsh you already know — sessions, tools, plugins, settings, themes. The frontend is upstream, untouched; the agent host runs locally, so there is no relay, no CORS, no account gate.
  • Nothing to render with — the system WebView draws the UI, so the package ships only the agent runtime (≈42 MB payload) instead of a browser engine. The HAP is ≈88 MB.
  • Installs without restricted permissions — the default build is JIT-free (compat), so side-loading needs no ACL-bound permission. A jit variant exists for devices granted the writable-code-memory permission.
  • Zero upstream changes — HarmonyOS differences live in an ohos profile, one bundle layer, seam plugins and six audited shims. Upgrading dsh means re-running the pipeline, not re-doing patches.
  • Branded as this product — own icon, name and window title; the upstream preview notice and the DeepSeek first-run dialog no longer open by themselves (both remain reachable in Settings).

Two HarmonyOS editions

HarmonyOS gets two independent editions with the same shell architecture, the same unmodified Web UI and the same data plane; the difference is which runtime provides Node:

HarmonyOS Edition (this repo) Electron on HarmonyOS Edition (dsh-desktop-hos)
Renderer The system ArkWeb — nothing bundled Chromium, shipped inside Electron 37
Node.js libnode.so started in the app's own process (v26.13.0) Inside the Electron runtime (Node 22.17)
Runtime plumbing @fellow99/node-bridge + @fellow99/node-runtime (ohpm) harmonypc-electron
Upstream dsh patches 0 — profile + bundle layer + audited shims 13 source patches
Install requirement none (JIT-free default) JIT restricted permission (ACL)
Package size ≈88 MB Electron-sized (hundreds of MB)
Maturity 0.2.2 — built (0.2.1 device-verified on HarmonyOS 6.1.0.135 / API 24) 0.2.2 — built & signed (on-device re-verification pending; 0.2.0 baseline)

Neither replaces the other: the Electron edition buys maximum desktop fidelity at the cost of a bundled Chromium and JIT; this edition buys a small payload and a permission-free install at the cost of covering platform gaps in the shim layer.

Capabilities at a glance

Area State
dsh Web UI, sessions, tools, skills, subagents ✅ works as upstream
File read / write / edit, image attachments ✅
Workspace picker with Documents & Downloads (grant → read/write) ✅
Git (21 tools, pure JS, no git binary needed) ✅
Local plugins loaded from the profile, own branding ✅
Command execution (bash) ⚠️ executor ships; a path-resolution fix is pending
Content search (grep / glob) ⚠️ needs a pure-JS backend (no ripgrep binary on arm64)
Delete / move / copy / chmod ⚠️ upstream ctx.fs has no such primitives yet
Plugin marketplace, tray icon, window-state memory — not in this edition

The complete matrix — every capability, both editions side by side, with root causes — is docs/鸿蒙环境能力清单-0.2.1.md.

Status

0.2.2 (versionCode 202) — built for dsh-v0.2.2-rc.1 on Node 26.13.0 (on-device verification pending; 0.2.1 device-verified on HarmonyOS 6.1.0.135 / API 24, 2in1): installs with zero ACLs, the payload self-extracts and reports ready, all shims install, node:sqlite/FTS5 available, text and image conversations, workspace picker across the three roots, git clone (public and intranet), and the branded window (checked through the WebView debugger). Known gaps and their fix points are listed in the capability inventory above.

Build

Prerequisites: DevEco Command Line Tools (SDK API 24) and the sibling submodule ../deepseek-harness. The Node runtime is pulled from the OpenHarmony ohpm central repository: @fellow99/node-bridge (API + NAPI bootstrap) and @fellow99/node-runtime@26.13.0 (the libnode.so engine, SHA-256-locked by the bundled runtime.lock.json).

node scripts/assemble-payload.mjs --deploy --apply   # ① materialize the dsh runtime
bash scripts/build-hap.sh           # ② ohpm install → payload archive + HAP build/sign
hdc app install -r entry/build/default/outputs/default/entry-default-signed.hap

OHOS_CLT overrides the toolchain root and accepts either layout: Command Line Tools (<root>/bin + <root>/sdk + <root>/tool/node) or a DevEco Studio install (<root>/tools/{hvigor,ohpm,node}/bin + <root>/sdk + <root>/jbr). node scripts/verify-upstream.mjs proves the upstream pin is intact (tag, clean tree, patch ids, brand/onboarding gates).

Signing (read this before wondering why a signed HAP fails)

assembleHap runs hap-sign-tool.jar via whatever java is first on PATH — the hvigor task does not pin a JDK. If the machine also has another JDK (sdkman/Temurin, Adoptium, …), signing dies with a misleading error that has nothing to do with the HAP:

Failed :entry:default@SignHap...
ERROR: 11012006 File IO failed
Error Message: Invalid CEN header (invalid zip64 extra data field size)

scripts/build-hap.sh therefore prepends DevEco's bundled JBR (with cygpath -u, otherwise MSYS bash cannot resolve java.exe) and exports JAVA_HOME. If you invoke hvigorw yourself, do the same or you will hit that error.

Signing material is never committed. Either let DevEco Studio generate it (it writes app.signingConfigs into build-profile.json5 — do not commit that file; revert it after building), or provide signing.debug.local.json / signing.release.local.json (gitignored) with plaintext passwords (certpath, storeFile, profile, keyAlias, keyPassword, storePassword, signAlg) — DevEco's encrypted password strings only decrypt on the inline build-profile.json5 path.

Run bash scripts/build-hap.sh --debug to get entry-default-signed.hap, which installs on a device whose debug profile matches (hdc app install -r …). --release needs a release profile and can only ship through AppGallery.

Docs

Document What it answers
Capability inventory 0.2.2 What works, what does not, and how this compares to the Electron edition
Engineering plan Why this architecture, what was rejected, and the shim whitelist
On-device notes What broke on the device and how it was diagnosed
JIT and ACL · JIT-less decision The two runtime forms and what each costs
Specifications 14 spec modules (013, 101–108, 110, 119, 202, 204, 205) with plans and gates

Related

  • dsh-desktop — Electron shell for Windows / Linux / macOS
  • dsh-desktop-hos — Electron on HarmonyOS Edition
  • @fellow99/node-bridge / @fellow99/node-runtime — the ohpm packages that embed Node (node::Start) in-process
  • deepseek-harness — the wrapped agent host

License

MIT

—/ 5

No ratings yet

Manifest verification required

Commit d459e904cf72

Community comments

No comments yet. Be the first to write one.

DSH HUB

A community index for DSH plugins. Not an official GitHub or DeepSeek AI product.

CommunityResourcesAPIAbout