@local/dsh-remote-control
适合手机的远程控制页面：列出会话、查看正在运行的一轮、发送提示词、回答问题。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Dynesshely/dsh-plugin-remote#db5106fe573a810f1d8c89683fd9a35437042909Remote Control 以 @local/dsh-remote-control 发布，当前版本为 1.0.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
DeepSeek Remote is a plugin for DeepSeek Harness that serves the desktop app's conversation as a web page, so you can read answers, send prompts and manage sessions from a phone, a tablet or another machine on the same network. It talks to the Host it runs inside — no separate daemon, no cloud relay — and every request is gated by a token you own.
Clone this repository and add it to your DSH profile as a bundle. cordis.patch.yml carries the ready
profile line (bind, port, token).
Start DSH. The Host log prints a URL you can open directly:
http://127.0.0.1:19400/?k=<token>
Open it on the device. ?k= is used once only — the page exchanges the token for an
HttpOnly; SameSite=Strict cookie and cleans the address bar.
The token is generated on first start and stored in ~/.dsh/remote-control/auth.json with 0600
permissions. Set token: in the config to pin your own instead.
- id: remote-control
name: '@local/dsh-remote-control'
config:
bind: '0.0.0.0' # 127.0.0.1 keeps it local; 0.0.0.0 exposes it to the network
port: 19400
token: '' # empty = generated once, then persisted
bind: 127.0.0.1 and reach it through WireGuard, Tailscale or an SSH
forward. Nothing is exposed, and the page still gets a secure context.bind: 0.0.0.0 and open http://<lan-ip>:19400/?k=<token>. Over plain HTTP on a
non-loopback address the browser treats the page as an insecure context: installing it as an app,
notifications and some clipboard APIs are unavailable. Terminate TLS in a reverse proxy if you need them.Direct LAN access also needs an inbound rule. The repository ships a script (needs administrator rights; it will raise a UAC prompt):
# allow inbound TCP 19400 for the Domain/Private profiles, local subnet only
pwsh -File plugins\remote-control\tools\firewall-remote-control.ps1
# remove the rule again
pwsh -File plugins\remote-control\tools\firewall-remote-control.ps1 -Remove
The rule is named DSH Remote Control (TCP <port>). It only opens the firewall — the listener still
follows bind, so the rule exposes nothing while bind is 127.0.0.1.
The Host serves ui/dist, so the SPA has to be built before it is used:
pnpm --dir plugins/remote-control/ui install
pnpm --dir plugins/remote-control/ui run build # emits ui/dist
Every suite is a standalone script; none of them needs DSH to be running. The integration suite boots the plugin in-process and drives it over real HTTP and SSE.
node plugins/remote-control/tools/test-remote-control.mjs # Host: auth, routes, SSE, models, permissions, attachments, paging
node plugins/remote-control/tools/test-remote-ui-store.mjs # transcript folding: tool groups, context notes, images
node plugins/remote-control/tools/test-remote-ui-questions.mjs # questions: argument/answer parsing, recommended flags
node plugins/remote-control/tools/test-remote-ui-rail.mjs # prompt rail: ticks, active detection, geometry
node plugins/remote-control/tools/test-remote-ui-layout.mjs # mobile detection: viewport vs overflow
node plugins/remote-control/tools/test-remote-ui-highlight.mjs # highlighting: language set, injection, Markdown pipeline
# read-only probe against a running instance
node plugins/remote-control/tools/smoke-remote-control.mjs http://127.0.0.1:19400 <sessionId>
host/hot.js and its siblings are imported with an mtime-derived query, so an edit takes effect on
the next HTTP request — POST /api/__reload forces it.index.js is part of the Loader's module generation: changes there need a DSH restart. Toggling
the bundle only re-applies the cached module.plugins/remote-control/
├── index.js Host half: HTTP server, auth, routes, SSE, static files
├── host/
│ ├── hot.js Hot-reloadable routes: session management, DSH control, presets
│ ├── usage.js Balance and usage aggregation, gateway first
│ └── model-meta.js Context windows, joined from the gateway's /v1/models
├── ui/ Vue 3 + Vite SPA
│ ├── src/components/ Transcript, composer, sidebar, usage card, model browser …
│ ├── src/lib/ Store, Markdown pipeline, lazy rendering, API client
│ └── public/ App icons
├── locale/ UI strings (en, zh)
├── tools/ Test suites, smoke probe, firewall and DSH control scripts
├── docs/poster.png README hero image
├── page.html Fallback page used when ui/dist is missing
└── package.json, cordis.patch.yml Bundle manifest and profile line
Every route except / and /healthz requires the session cookie or Authorization: Bearer <token>.
| Route | Purpose |
|---|---|
GET /healthz | Unauthenticated liveness check |
POST /api/login, /api/logout | Exchange the token for a cookie, and back |
GET /api/state | Sessions, workspaces, pending interactions, bind info |
GET /api/stream?sessionId= | SSE: hello, pending, sessions, frame, stream-error |
GET /api/models, POST /api/select-model | Model catalogue and switching |
GET /api/older?sessionId=&beforeSeq= | One page of older history ({ records, hasMore }) |
GET /api/attachment?sessionId=&attachmentId= | Image bytes from a session log |
| `GET /api/image?url= | path=` |
GET /api/usage, POST /api/usage/config | Balance and usage, plus its configuration |
GET /api/model-meta | Context windows per model id |
GET /api/dsh/info, POST /api/dsh/restart, /api/dsh/exit | Describe, restart or quit DSH |
POST /api/send, /api/cancel, /api/answer | Send a prompt, stop a turn, answer a question |
GET /api/permissions, POST /api/permission | Permission presets and switching |
/api/* route; comparisons are constant-time, and both the session cookie
and an Authorization: Bearer header are accepted.default-src 'none' with frame-ancestors 'none'.Released under the GNU Affero General Public License v3.0. In short: use it, change it, share it — but if you run a modified version as a network service, you have to offer its source to the people using it.