JavaScript DSH plugin that turns a phone into a remote control for the desktop: QR / 6-digit / remote pairing codes, a LAN service on port 8899, an frpc tunnel for off-network access, two status lamps and a version card with upgrade and rollback. The repo metadata declares no license; the README ends with MIT.
DSH integration
Native runtime
Author-claimed
Safety audit
Unaudited
Last verified
2026-11-16
License
Not specified by the author
01What can it help you accomplish?
Drive a DSH desktop session from a phone — read the session list, send and receive messages, browse history and move files — on the same network or from somewhere else
A paired HarmonyOS app talking to the plugin's LAN service on port 8899: `/sessions` for the session list, `/cmd` for sending and receiving, model switching, file browsing, the plugin list, the queue and upgrades, `/attachment` for files — all behind the access code — or the same traffic over an frpc tunnel when the phone is off-network
People who keep DSH running on a desktop or a cloud server and want it reachable from a phone without a remote-desktop app
Pair a phone without typing an IP address, and keep the exposure short-lived
A QR code with a one-time ticket inside, a 6-digit code the app uses to find the computer on the same network, or a 6-digit remote pairing code when the DSH host is somewhere else
Anyone pairing over home or office Wi-Fi, and people running DSH on a cloud server where the LAN address inside the QR code is not reachable
Keep the DeepSeek web chat open beside the session instead of switching windows
A 网页聊天 tab in the right sidebar that loads chat.deepseek.com, with a 重新加载 button when the webview fails
DSH desktop users who also work in the web chat and do not want it in a second browser window
02How to install into DeepSeek Harness
Prerequisites
- Phone side: the HarmonyOS app 「DSH控制台」, downloaded only from the app store — this repo ships no installer package
- A profile name after `--profile`: the argument is mandatory, and omitting it fails with `required option '--profile <name>' not specified`
- Do not add the `insert` line to the profile's `cordis.patch.yml` again — the package already carries it, and a duplicate loads the plugin twice
- Optional: the public access service, needed only when the phone is not on the same network as the computer
Installation steps
- 01
Run `dsh plugin --profile web add dsh-console-hm`, replacing `web` with your own profile name (`web` is the default).
$ dsh plugin --profile web add dsh-console-hm
- 02
If a just-published version installs the previous one, retry with the version pinned and pnpm's minimum release age off: `dsh plugin --profile web add dsh-console-hm@latest --config.minimumReleaseAge=0`
$ dsh plugin --profile web add dsh-console-hm@latest --config.minimumReleaseAge=0
- 03
Or install from the plugin page: DSH sidebar → 插件 → 「添加插件」 → pick `dsh-console-hm-<version>.tgz`.
- 04
For development, link the folder instead: put `"dsh-console-hm": "link:<absolute plugin path>"` into the profile's `package.json` dependencies, add `"dsh-console-hm"` to its `dsh.profile.bundles` array, then run `pnpm install`.
- 05
Tuning (usually unnecessary) lives in the profile's `cordis.patch.yml` under `- id: dsh-console` → `config`: `port` for the LAN service port, `name` for the node name the panel shows (default is the system host name) and `allowShiftPort`.
Verify the integration
- Open 设置 → 导航列表 → DSH控制台, or the sidebar entry, and read the two lamps: the DSH lamp says whether this computer's session service is reachable, and a grey phone lamp only means no phone has paired yet — not an error.
- From a source checkout run `node test/selftest.mjs`: it needs no DSH installation, covers 10 groups and occupies ports 18777 and 18888, never 8899, so it can run while the plugin is running.
- The panel's version card shows the npm version, so you can confirm an upgrade actually landed.
Rollback
- Roll back from the panel's upgrade card: `[ 检测更新 ] [ 升级 ] [ 回滚 ]`.
03DSH integration and capability boundaries
DSH plugin, package name `dsh-console-hm`: install with `dsh plugin --profile web add dsh-console-hm`, and it mounts a panel at 设置 → 导航列表 → DSH控制台 plus two sidebar entries; its panel routes (`/api/dsh-console/state`, `/newcode`, `/sessions`, `/cmd`) are registered through DSH's own `connection.fetch.register` and sit behind DSH's browser auth, while a separate LAN service on port 8899 serves the phone app
QR pairing with a one-time ticket
a QR PNG from `/qr`; the payload is `dsh-console://pair?b=…&k=pt_…&n=…&i=dsh-console&c=…&v=…`, where `k` is a one-time pairing ticket rather than the long-lived access code
every refresh mints a new ticket and a new `v` value, so the QR image really is redrawnthe long-lived access code never appears in the QR payload6-digit and remote code exchange
an access code from `/claim` — a wrong code answers 403, a malformed one 400, too many attempts 429, and a successful claim burns the code
the code is dead as soon as it has been exchanged for an access coderemote pairing has to be switched on first, and its 6-digit code rotates every 15 minutesPublic access through an frpc tunnel
a tunnel the plugin starts itself once the public access service is enabled, so a phone on cellular data can reach the machine
downloads `frpc` into `~/.dsh/frp` (`frpc.exe` on Windows) and checks size then sha256 before anything is writtenan frpc binary you placed there by hand always wins and is never overwrittenusers who never enable public access get no download, no process and no extra panel cardTwo independent status lamps
one lamp for the phone (the App sends a heartbeat every 60 s while in the foreground, and a request within the last 10 minutes counts as connected) and one for DSH (whether the in-process session service can be reached)
a grey phone lamp is a normal state, not an errorVersion card with upgrade and rollback
the current version plus 检测更新 / 升级 / 回滚, backed by the npm version check
升级 and 回滚 replace the installed plugin version
04Who is it for? When not to use it?
Good for
- People who keep DSH running on a desktop or a cloud server and want it reachable from a phone without a remote-desktop app
- Anyone pairing over home or office Wi-Fi, and people running DSH on a cloud server where the LAN address inside the QR code is not reachable
- DSH desktop users who also work in the web chat and do not want it in a second browser window
Not for
- The phone side is the HarmonyOS app 「DSH控制台」, distributed only through the app store — this repo ships no installer — and pairing never happens in a browser: `/`, `/pair`, `/web` and `/pet` all answer 403.
- The LAN service defaults to port 8899 and the 6-digit path only probes 8899, so a busy port makes the plugin fail to start and log what to do instead of quietly moving; changing `port` means changing the phone side too, and only `allowShiftPort: true` restores the 20-port fallback.
- Remote pairing needs the public access service first and is off by default; while it is on, anyone who knows the public address can try — tickets last 5 minutes, remote codes expire after 15, 20 wrong attempts from a public source lock for 15 minutes, and the README advises switching the gate off after pairing.
- Whoever holds the access code on the same network can operate this computer's DSH; the routes that control DSH always require it, it changes on every process restart, and the `/api/dsh-console` panel routes sit behind DSH's own browser auth, so bare curl answers 401.
05Compatibility, maintenance and safety notes
- The phone side is the HarmonyOS app 「DSH控制台」, distributed only through the app store — this repo ships no installer — and pairing never happens in a browser: `/`, `/pair`, `/web` and `/pet` all answer 403.
- The LAN service defaults to port 8899 and the 6-digit path only probes 8899, so a busy port makes the plugin fail to start and log what to do instead of quietly moving; changing `port` means changing the phone side too, and only `allowShiftPort: true` restores the 20-port fallback.
- Remote pairing needs the public access service first and is off by default; while it is on, anyone who knows the public address can try — tickets last 5 minutes, remote codes expire after 15, 20 wrong attempts from a public source lock for 15 minutes, and the README advises switching the gate off after pairing.
- Whoever holds the access code on the same network can operate this computer's DSH; the routes that control DSH always require it, it changes on every process restart, and the `/api/dsh-console` panel routes sit behind DSH's own browser auth, so bare curl answers 401.
MIT per README, none in repo metadata · release tag ffmpeg-2026-11-09 · README claims, not independently audited
06Frequently asked questions
How do I install dsh-console-plugin into DeepSeek Harness?
Run `dsh plugin --profile web add dsh-console-hm` — the npm package is `dsh-console-hm`, not the repo name — replacing `web` with your own profile name. The `--profile` argument is mandatory: leaving it out fails with `required option '--profile <name>' not specified`. If the just-published version installs the previous one, pin it and drop pnpm's minimum release age: `dsh plugin --profile web add dsh-console-hm@latest --config.minimumReleaseAge=0`.
Where does the panel show up inside a DSH session?
Under 设置 → 导航列表 → DSH控制台, in the plugin page's configuration area, and as two sidebar entries: 「DSH控制台」 opens the panel and gains an update badge when a new version exists, 「网页聊天」 opens chat.deepseek.com in the right sidebar and works on the desktop client only, because it needs the host webview channel.
What network exposure does it create?
A LAN HTTP service on port 8899 whose requests carry `?token=<access code>` or an `x-dsh-console-token` header; `/sessions`, `/cmd` and `/attachment` refuse to work without one. Remote pairing is off by default and needs the public access service; public-source requests may only use the access-code routes. The panel's own routes live under `/api/dsh-console` and go through DSH's `connection.fetch.register`, so a bare curl gets 401 by design.
Do I need the phone app, and does it run through the browser instead?
The phone app is required: the HarmonyOS app 「DSH控制台」 from the app store, and this repo ships no installer package. There is no web pairing page either — `/`, `/pair`, `/web` and `/pet` all answer 403 — so pairing only happens through the app.
How can I check the plugin works without installing it into DSH?
Run `node test/selftest.mjs` in a source checkout. It needs no DSH installation, checks 10 groups (payload format, one-time codes, real QR output, `/claim`, the deleted pairing page, the 401/403 boundary, the busy-port error, both halves of the client/host contract and the package manifest), and occupies ports 18777 and 18888 while never touching 8899 — so it can run with the plugin live.
07Related DSH workflows
ds-harness-remote
by liguobao
Lets authorized desktop, web, and Android clients operate a remote Harness host.
dsh-windows-mcp
by hellohub1212
Windows desktop automation for DeepSeek Harness: the in-box MCP client bridge mounted against CursorTouch/Windows-MCP, with an off-by-default Computer Use switch and an in-app dependency installer.
dsh-desktop
by anywhere-labs
Modern desktop client for the DeepSeek Harness (dsh) plugin ecosystem. Everything is a plugin — even the desktop shell itself.
dsh-go
by ccch1mneyyy
Run DeepSeek Harness on your phone and remotely control your desktop from a native Android app.
08Data and sources
dsh plugin --profile web add dsh-console-hm
挂在 **设置 → 导航列表 → DSH控制台**,也挂在**插件页**的配置区,侧栏底部还有两个入口。
前缀 `/api/dsh-console`,走 DSH 自己的 `connection.fetch.register`,
**带 DSH 的浏览器认证层**,所以裸 curl 会 401 —— 这是对的,不是 bug。
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-16. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.
