dshmobile — Remote Mobile Client for DeepSeek Harness

中文文档

Zero-friction: install the plugin once → scan a QR code → keep working from your phone. A true Remote Client for DSH — no Tailscale, tunnels, port forwarding, NAT, or networking knowledge required, no DSH modifications, cross-platform.

Control your local DeepSeek Harness (DSH) from your phone: scan to pair → device → session tree → chat, approvals, question answering, model switching, file browsing.

Architecture

┌──────────────┐   WSS    ┌───────────────────┐   WSS    ┌───────────────────────────┐
│ Android App  │ ───────▶ │  Cloud Relay       │ ◀─────── │ PC Bridge (DSH plugin)     │
│ (signed APK) │          │ (hosted service)   │          │ (open source)              │
└──────────────┘          └───────────────────┘          └────────────┬──────────────┘
                                                                       │ 127.0.0.1:3080
                                                             ┌─────────▼──────────┐
                                                             │ DeepSeek Harness   │
                                                             └────────────────────┘

Business content (prompts / replies / sessions / files) is protected by E2EE end-to-end encryption: the relay only sees routing metadata — it can neither read nor tamper with your session content. The connection layer self-heals: after a DSH restart or a network hiccup it re-handshakes automatically, no manual steps required.

Open Source & Security

The protocol and crypto implementations are fully public and independently auditable; business content is end-to-end encrypted, and the relay only forwards routing metadata — it cannot read your sessions.

Installation

Pick your path first: DSH desktop app 0.2.0 or newer → §A (GUI, recommended); legacy dsh web (0.1.7) → §B (CLI). Both install the same package @zdx8637/dshmobile-bridge (current plugin version 1.0.7).

A. PC — DSH 0.2.0 desktop app: install from the GUI (recommended)

1. Open the DSH desktop app → plugin manager → click 「添加插件」 (Add plugin);

2. Paste the package name with an exact version into the input box (its placeholder reads 「输入插件的包名、GitHub 仓库地址或本地目录路径。」 — a GitHub repository URL or a local directory path is accepted there too):

   @zdx8637/dshmobile-bridge@1.0.7

3. On the right pick 「安装源」 — npm 官方源 (official npm registry) or 中国大陆镜像源 (Mainland-China mirror) — whichever your network reaches;

4. Click install;

5. Restart DSH — the host has to reload the plugin before it takes effect;

6. Open the panel: a ▶ arrow appears at the bottom of the web sidebar — click to open it (① login / grant code, ② encrypted pairing code).

⚠️ Always pin an exact version (e.g. @zdx8637/dshmobile-bridge@1.0.7). The profile directory contains a pnpm-lock.yaml; when you reinstall by bare package name the lockfile can pin the version back to the old one (measured: npm already served 1.0.2, yet a reinstall still left 1.0.0 installed).

⚠️ Plugins do not auto-update. The dialog says so outright — 「插件安装后，暂不支持自动更新。若需升级，请先卸载再安装新版」. So to upgrade: uninstall in the plugin manager first, then repeat the steps above with the new version number.

B. PC — DSH 0.1.7 (legacy: dsh web + CLI): install from the CLI

npx -y @deepseek-ai/dsh plugin --profile web add @zdx8637/dshmobile-bridge@latest
# after restarting dsh, a ▶ arrow appears at the bottom of the web sidebar — click to open the panel

Requires pnpm (the dsh plugin subcommand depends on it; corepack enable or npm i -g pnpm). Legacy only: npm latest for @deepseek-ai/dsh points at the 0.1.7 CLI, so this command pulls the 0.1.7 dsh plugin. On 0.2.0 or newer use §A (the GUI) instead — the CLI is not the 0.2.0 install path.

Phone (Android App)

Scan the QR code on the PC panel → download the signed APK from the landing page (current version v1.0.0). Then scan in the App: ① first to log in, ② then for E2EE pairing — once paired, a shield badge appears in the device list (E2EE is active). A shield with a slash means plaintext; both are grey — the difference is the shape, not the colour.

DSH Version Requirement

The plugin supports the v2 protocol only, i.e. DSH v0.1.5 or newer. The legacy protocol for older DSH builds was removed entirely in 0.1.0-beta.23.

This is a deliberate narrowing: the dual-protocol branch was a long-standing defect hotspot, since every change had to be verified on both paths. If you are still on a pre-v2 DSH, stay on 0.1.0-beta.22, or upgrade DSH first.

Directory

Trust & Self-hosting (roadmap)

• Today the relay is a hosted service operated by the author; content privacy is guaranteed by E2EE, and the relay only routes and forwards metadata.
• A reference self-hosted relay (reference implementation, ≠ the production service) will be released later so you can self-host: Android → self-hosted relay → Bridge → DSH. Account system, monitoring, and scaling remain the operator's concern.

Privacy & Secrets

This repository contains no real credentials. Android signing keys, relay account passwords, and server SSH credentials live only in local/private channels — always injected via environment variables and referenced as placeholders in docs.