DSH Marketplace

dsh-remote-web-ui

zhu1090093659/dsh-web#packages/dsh-remote-web-ui

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.

8,594561TypeScriptApache-2.0Source

Install

Add dsh-remote-web-ui to DeepSeek Harness

Install into

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.

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 4d agoon DeepSeek Harness 0.2.2-rc.1.

Show it in your README

install verified — dshmarketplace

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

Before you install dsh-remote-web-ui

  • Source of record: zhu1090093659/dsh-web — present in the community registry that DSH's own plugin market installs from.
  • Licensed under Apache-2.0.

Security

What installing dsh-remote-web-ui runs

Build scripts

pnpm skipped these dependency build scripts, and the plugin registered without them:

  • cloudflared@0.7.3

Under pnpm 11 the install stops and asks you to approve them instead; an approved script runs with your user account's permissions.

Source: our sandbox install on DeepSeek Harness 0.2.2-rc.1, 4d ago.

Install hooks

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.

README mentions

Neither shell commands nor credentials.

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.

The AI take

What it is — Adds a phone and second-PC front-end onto a live DSH Web workspace, using QR pairing behind a token gate, SSE for live updates, and two GUI modes.

Who it is for — An agent job is still streaming in DSH Web on the machine you just left, and you need to keep reading it or send the next instruction from a phone or another PC. If the work never leaves the DeepSeek Harness CLI, skip this: there is no web workspace for pairing to attach to.

Watch out — The sandbox only showed a clean-profile install that DSH registered; QR pairing, live sync, and both GUIs were not run. The family README names WebSocket where this package blurb names SSE — go by what actually runs.

The verdict — I would spend the plugin slot only when an unfinished workspace has to travel with me, not to get another place to start new chats.

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.

What dsh-remote-web-ui does

Abstract diagram of a token-gated stream branching into mobile and desktop remote-control paths.

dsh-remote-web-ui is a DeepSeek Harness plugin that lets a phone or another computer control a DeepSeek Harness web workspace remotely. DeepSeek Harness presents a pairing flow based on a QR code: the remote device joins a token-gated channel, then receives workspace changes through Server-Sent Events (SSE). The remote interface is available in two forms: a mobile GUI intended for phone-sized touch interaction, and a full desktop GUI for PC browsers.

dsh-remote-web-ui is for operators who need to reach an existing dsh web workspace from another device rather than remain at the host computer. The remote connection can expose the same workspace actions available through the web interface, so the paired device should be treated as another client of the agent environment and its permissions.

This is not a standalone workspace or a replacement for dsh web. It is the wrong choice when local browser access is sufficient, when remote pairing is not acceptable, or when the target environment does not provide the web workspace that the plugin controls. The supplied documentation describes the pairing, token channel, SSE synchronisation, and GUI modes, but does not specify additional configuration keys or files that dsh-remote-web-ui reads or writes.

dsh-remote-web-ui documentation

Configuring dsh-remote-web-ui

DeepSeek Harness loads dsh-remote-web-ui as part of the web profile, where it controls an existing dsh web workspace. The documented setup is pairing from the remote interface: scan the displayed QR code, then use the token-gated channel established for that pairing. The supplied README does not define plugin-specific configuration keys, default values, environment variables, or data files.

How dsh-remote-web-ui behaves

After pairing, the remote client receives workspace updates through Server-Sent Events (SSE). The channel is gated by a token rather than being described as an open endpoint. The plugin provides two remote GUI modes:

  • a mobile GUI for phone-oriented use;
  • a full desktop GUI for remote PC browsers.

The README's broader project documentation describes this capability as remote control of a dsh web workspace across phones, tablets, and other computers. The plugin therefore operates on the host workspace exposed by DeepSeek Harness rather than creating a separate agent workspace.

Requirements for dsh-remote-web-ui

DeepSeek Harness must have a web workspace for the plugin to control, and the remote device must be able to reach the pairing channel. The documentation identifies dsh web and the web profile as the relevant host context. It does not state a minimum DeepSeek Harness version, a supported browser list, or platform-specific requirements.

Known limits of dsh-remote-web-ui

dsh-remote-web-ui is a remote-access layer, not a standalone replacement for dsh web. Its documented scope is pairing, token-gated communication, SSE synchronisation, and the two remote GUI forms. The README does not document a plugin-specific command, additional persistence format, or controls for changing the permissions of the workspace being operated.

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

Alternatives to dsh-remote-web-ui

dsh-ssh

zhu1090093659

8.8k

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

npm packageTypeScript24d ago

AI review

dsh-ssh

What it is — Adds a browser SSH terminal, progress-tracked SFTP, local port forwarding, and cross-host one-shot execution to DSH, with agents reusing that host list.

Who it is for — You send DeepSeek-V3 or DeepSeek-R1 agents at Linux boxes from DSH, and the session cannot reach those hosts. If DSH is only local coding and chat for you, and SSH stays in your own terminal or jump host, this panel sits off your path.

Watch out — In a blank profile it installed and DeepSeek Harness registered it. Nothing on the panel itself was exercised in that run. No install-level snag showed up.

The verdict — I'll turn it on now and keep production hosts out of the profile until a throwaway machine proves the session can actually land.

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.Read the source
Details

dsh-ssh

zhu1090093659

8.6k

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

npm packageTypeScript1mo ago

AI review

dsh-ssh

What it is — A DSH panel for an in-browser SSH shell, SFTP with progress, local port forwarding, and one command run across many hosts.

Who it is for — You have DSH agents changing configs, moving files, or debugging a live Linux service, and stock dsh web has no remote-ops surface. Leave it if the work stays in a local repo plus chat, and every server is handled by tools that never touch DSH.

Watch out — A blank-profile install succeeded and DSH registered it into that profile. No obvious traps.

The verdict — I'll add it. One host list for the panel and the agents is the part I will not keep in two places.

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.Read the source
Details
1.9k

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

npm packageTypeScript4d ago

AI review

ds-harness-remote

What it is — Keeps DeepSeek Harness running on the work machine and joins that same session from a phone, browser, or another PC over an end-to-end encrypted channel, with workspace files, read-only previews, and a remote terminal.

Who it is for — A desk host already has models and workspaces configured in DeepSeek Harness, and you keep continuing that session from a phone or a second computer without exposing a public listener. If Harness only ever runs on the machine that travels with you, there is no separate Host to open.

Watch out — It installed on a fresh profile and DeepSeek Harness registered it. An API key or token must be provided. iOS is TestFlight-only, with no public release.

The verdict — I would enable it when the far end can be Android, Web, or DeepSeek Harness Desktop, and I would not enable it for an iPhone-only remote screen.

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.Read the source
1Details

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

GitHub sourceTypeScript14d ago

AI review

deepseek-harness-remote

What it is — Joins a phone, browser, or second computer to the DeepSeek Harness session that is already running on your Host, over an end-to-end encrypted channel.

Who it is for — A DeepSeek model job is live on the office tower—workspaces and tools already wired—and you still need that exact thread after you walk away. If the only Harness you use already sits in the backpack that leaves with you, remote access is not the missing piece.

Watch out — A fresh profile install completed and DeepSeek Harness registered the plugin. You must supply an API key or token; setup runs shell, and the Linux script path runs the Host as root. The catalog text (ApiProxy-only, read-only preview, no shell or writes) does not match the README list of remote terminals and dev-service previews—trust the live session; iOS is still unreleased TestFlight.

The verdict — Worth it on a machine that never sleeps. I am not putting DeepSeek Harness on a public listener just to peek at a session from the couch.

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.Read the source
2Details

dsh-mobile

saya-ch

479

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.

Installed cleanly when we ran it

npm packageTypeScript25d ago

AI review

dsh-mobile

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.

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.Read the source
1Details

dsh-ios

ZSeven-W

360

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

npm packageTypeScript1mo ago

AI review

dsh-ios

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.

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.Read the source
1Source