dsh-remote-web-ui

What it is — A DSH plugin that exposes a web terminal, progress-tracked SFTP, local port forwarding, and the same command across many hosts, with agents on that shared host config.

Who it is for — You run DeepSeek-V3 or DeepSeek-R1 in dsh web and want an agent to inspect a Linux box, move files, or open a local forward; stock dsh web has no server-ops surface. Keep it off if jump hosts and runbooks already live outside Harness and you only open DSH to write code or talk.

Watch out — It installed on a clean profile and DeepSeek Harness registered it. Live SSH to a real host was not exercised. No obvious pit showed up in that pass.

The verdict — This one goes on the profile by itself; I would not pull in the rest of dsh-web just to get an ops panel.

What it is — Gives DSH a browser SSH terminal, SFTP with progress, local port forwarding, and one-shot commands across hosts; agents share one host config.

Who it is for — Fits a DSH agent that must log into remote Linux to change configs, push files, or chase a live service when the stock UI has no SSH surface. Leave it out if the agent stays on the local workspace and you already jump boxes from a separate SSH client.

Watch out — The sandbox only showed a clean install on a fresh profile and that DSH registered it. No real host was attached, so the terminal, SFTP, forwards, and cluster path were not proven. No install-level issue showed up.

The verdict — I'll take that swap: fewer outside terminals, ops stay inside the DSH session.

What it is — It continues a live DeepSeek Harness session on your phone, browser, or another computer over an end-to-end encrypted channel.

Who it is for — Desktop or dsh-TUI is still holding workspaces and an unfinished thread, and you need that same session on Android or the web after you leave the desk. If every conversation already lives in the cloud and no local Host exists to attach to, this plugin does not create a remote environment from nothing.

Watch out — A clean-profile sandbox install succeeded and DeepSeek Harness registered the plugin. Source installs run scripts and expect an API key or token; the Linux path runs Host processes as root, intended only for trusted accounts. iOS is still an unreleased TestFlight, and the Chrome extension only mints a device credential—it does not host a conversation UI.

The verdict — I would add it as a second window onto a machine that is already the Host; I would not treat it as remote desktop or a standalone mobile agent.

What it is — Hooks a running computer-side DeepSeek Harness into an Android App or a phone browser so the live session continues after pairing.

Who it is for — A DeepSeek Harness job is still using tools on the PC, you have left the desk, and you need that same workspace on the phone. Do not enable it where a phone cannot be a fully trusted operator of that machine, or where the host cannot expose its own LAN or remote HTTPS endpoint.

Watch out — Fresh-profile install succeeded and DeepSeek Harness registered the plugin into the profile. On DSH Desktop you must quit from the app menu after install; dsh-mobile-question-fixes: failed to import is documented and a normal restart may not clear it. The native App is Android-only; from 0.6.2 the plugin and App ship on separate clocks, and a self-signed FRP front-end still needs App 0.4.6 to pin the remote CA at pairing.

The verdict — Put it on a host that already stays up for DSH; I would not add Funnel, cpolar, cloudflared, or FRP only to check a session from outside.

What it is — Hooks an iOS Simulator or USB iPhone into a DeepSeek Harness conversation: 22 tools drive the device, and a sidebar shows a live stream you can tap and drag.

Who it is for — You're on a Mac using DeepSeek Harness on iOS / SwiftUI work, and you need the agent to build an Xcode project or Swift package, tap by accessibility tree or OCR, verify list-row actions via counters, and hot-reload SwiftUI previews. Leave it off non-macOS harness hosts: the tools still register, then fail with an explanation.

Watch out — In the sandbox it installed on a fresh profile and harness registered it. It executes shell on the machine. A real phone must stay unlocked; taps are gated by identify-before-tap; the plugin builds and launches WebDriverAgent and loopback-tunnels control and MJPEG. Frames reach the UI only through HMAC-signed URLs on the DSH webserver that expire in about 10 minutes.

The verdict — I'll pin 0.1.0-rc.10 to DSH 0.1.5-rc.1 — RC is what I pay to hand device control to the agent.

What it is — A multi-device remote access solution for DeepSeek Harness, enabling PC, Android, and Web clients to securely access and operate a remote Harness over low-latency, end-to-end encrypted P2P-first network.

Who it is for — If you use DeepSeek Harness on the web profile and need to access or operate sessions remotely from PC or Android devices, install ds-harness-remote. If you are using DSH Desktop, the remote feature is included by default and no separate plugin installation is required.

Watch out — Sandbox test passed in a new profile, where it was registered by Harness into the profile. It requires providing an API key or token. When installing from source, the build script needs to be manually whitelisted first.

The verdict — I would install it because it enables seamless session switching across devices without interruption, but currently only the hosted relay is supported, with self-hosted options not yet available.