dsh-ssh
zhu1090093659
SSH ops panel for DSH: web terminal, SFTP transfer with progress, local port forwarding, and one-command cluster execution across hosts; agents share the same host config.
Installed cleanly when we ran it
saya-ch/dsh-mobile
Access DeepSeek Harness from the Android app or a mobile browser with secure LAN and remote connections, persistent device pairing, and a customizable mobile interface.
Install
via npm
Resolves a published tarball rather than cloning the repository, and installs without any extra setup. Swap `web` for your profile name if you run another one.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/web/pnpm-workspace.yaml.
The desktop app keeps its own profile, desktop, and only the dsh command it ships may change it — the npm-installed dsh refuses that profile. Install the command from the app menu (Manage dsh Command…), open Desktop once, quit it fully, run the line below, then reopen Desktop.
via npm
Resolves a published tarball rather than cloning the repository.
via GitHub · npm package
Installing from GitHub runs the project's build script, which pnpm blocks until you allowlist it — run the command once and pnpm prints the exact key to add under `allowBuilds` in ~/.dsh/profiles/desktop/pnpm-workspace.yaml.
Our install check ran in a web profile on npm's dsh, not in the desktop app.
What happened when we ran it
Installed cleanly when we ran it
Every command here is run in a throwaway container against a clean profile, and the result is whatever the harness recorded — not a guess from the source. Last run 8d agoon DeepSeek Harness 0.2.2-rc.1.
Show it in your README
For maintainers: the badge serves this listing's latest sandbox verdict, so a re-run updates it on its own — and it links readers to the full result here.
Due diligence
Security
No build script was blocked in our run.
Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 8d ago.
package.json declares no preinstall, install or postinstall script.
Source: package.json on GitHub, read at our last sync. prepare is not recorded; it runs only on a GitHub install, and shows up under build scripts when pnpm blocks it.
shell commands (bash, exec, spawn …)
Source: a keyword match on the README — a hint about what the plugin touches, not an analysis of its code.
Not an audit. These are the record of one install and two text scans; nobody has read this plugin's code on your behalf. Plugins run with your agent's permissions.
What it is — DSH Mobile allows mobile browsers and Android apps to securely access DeepSeek Harness via LAN or remote connections while synchronizing sessions and workspaces.
Who it is for — If you want to use DeepSeek Harness for dialogue and tool operations on an Android device, dsh-mobile is suitable. If you primarily use DeepSeek Harness on the desktop, you don't need to install it.
Watch out — Sandbox testing passed: after installation in a new profile, it was registered by harness. It executes shell commands. No obvious issues found.
The verdict — I would install it because it supports persistent device pairing for mobile access to DeepSeek Harness.
Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

dsh-mobile is a DeepSeek Harness plugin that provides mobile access to a computer's DeepSeek Harness sessions, workspaces, messages and tools through an Android app or mobile browser. DeepSeek Harness loads dsh-mobile as a web-profile plugin; the plugin runs a separate mobile HTTPS endpoint and pairs devices using a QR code, link or key. Its settings, certificates, paired devices and custom files are stored under $DSH_HOME/mobile-access/. dsh-mobile setup configures the LAN address, while dsh-mobile setup --port changes the mobile listener from its default port of 3443; the upstream DeepSeek Harness web port is controlled separately with dsh web --port.
DeepSeek Harness users who need to continue work away from a desktop can use a local network connection or an optional remote route through Tailscale Funnel, cpolar, cloudflared, self-hosted FRP or a reverse proxy. The Android app is native; a browser can be used instead, but LAN access may show a private-certificate warning. Windows and Linux x64 can use plugin-managed Caddy HTTPS and certificates.
This is not a suitable choice where mobile access is unnecessary, where a trusted LAN or reliable HTTPS remote route cannot be provided, or where Android support is required but only a non-Android device is available. The terminal-surface risk is material: a paired device can operate the computer's DeepSeek Harness, including its sessions, workspaces and tools. Treat paired devices as fully trusted and revoke lost devices from the computer.
DeepSeek Harness loads dsh-mobile in the web profile. Run dsh-mobile setup to select and remember the current LAN address. Use dsh-mobile setup --address 192.168.x.x only when automatic selection fails, or dsh-mobile setup --port to change the mobile HTTPS listener from 3443. The upstream DeepSeek Harness Web port is changed separately with dsh web --port; dsh-mobile follows that port automatically. Settings, certificates, devices and custom files are stored in $DSH_HOME/mobile-access/.
The DeepSeek Harness mobile-access panel separately controls LAN and remote access and their pairing authorisations. It can generate a pairing key and QR code, or copy a pairing link. A browser can use the link without the Android app. Remote access is optional and can use Tailscale Funnel, cpolar, cloudflared, self-hosted FRP or an owned reverse proxy. On Windows and Linux x64, dsh-mobile can manage Caddy HTTPS and certificates.
The native app supports Android 10+. The phone can instead use a mobile browser. LAN access requires the phone and computer to share a trusted network; remote access requires a reliable HTTPS route. LAN uses a private CA, while public remote routes use system-trusted certificates. Credentials are kept in the Android Keystore, device tokens are sent only to the exact Origin, and third-party WebSocket connections are blocked by default.
A paired device is fully trusted and can operate the computer's DeepSeek Harness, so lost devices should be revoked immediately. Remote providers may impose bandwidth or connection limits. LAN and remote access are independent, and the remote service is disabled by default. The plugin does not modify DeepSeek Harness source code.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub
Same category
zhu1090093659
SSH ops panel for DSH: web terminal, SFTP transfer with progress, local port forwarding, and one-command cluster execution across hosts; agents share the same host config.
Installed cleanly when we ran it
zhu1090093659
Remote control of a dsh web workspace from phone or PC: QR-code pairing through a token-gated channel, SSE real-time sync, and separate mobile and full desktop GUI modes.
Installed cleanly when we ran it
zhu1090093659
SSH ops panel for DSH: web terminal, SFTP transfer with progress, local port forwarding, and one-command cluster execution across hosts; agents share the same host config.
Installed cleanly when we ran it
liguobao
Multi-device remote access for DeepSeek Harness and supported coding workspaces through an end-to-end encrypted channel, with adaptive Relay/WebRTC transport, device authorization, workspace files, read-only previews, terminals, and optional Codex Remote.
Installed cleanly when we ran it
liguobao
Multi-device remote access for DeepSeek Harness: continue an active session from your phone, tablet, browser, or another computer over an end-to-end encrypted channel (Noise IK + adaptive relay/WebRTC transport), with device authorization, ApiProxy-only remote capabilities, and read-only file preview via dsh-file-viewer — no shell, remote desktop, or write access.
Installed cleanly when we ran it
ZSeven-W
A live iOS Simulator or USB-connected iPhone inside the conversation: 22 agent tools for booting, building, driving the UI by accessibility identity or OCR text, list-row actions and SwiftUI preview hot reload, plus a streaming sidebar panel you can tap and drag on.
Installed cleanly when we ran it