DeepSeek Harness plugin

dsh-remote-access-web

Remote-access bundle for the DSH browser surface: mounts the reverse-tunnel host plugin and pins the directory picker to the in-app browse dialog so a remote operator can add workspaces

Jump to install

Source facts

Repository
wikkd/dsh-remote-access-web
Latest update
Aug 14, 2026
Category
Tools & Capabilities
GitHub stars
2
Format
plugin
Package path
packages/bundle/remote-access-web
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
packages/bundle/remote-access-web/package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/wikkd/dsh-remote-access-web/tree/HEAD/packages/bundle/remote-access-web
Plugin: dsh-remote-access-web
Author: wikkd

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer4 files
README.mdSource · read only
README language

@froststarinquire/dsh-remote-access-web

English | 中文

The dsh browser-surface remote-access bundle. [cordis.patch.yml](cordis.patch.yml) rides over the official dsh-web-app surface: it inserts the @froststarinquire/dsh-remote-access host row, which manages an outbound reverse tunnel so a remote device can reach the harness web service. The tunnel backend is selected by the provider config; the shipped driver is the frp provider (provider: 'frp'), running an frpc-compatible client. The browser surface (phone drawer layout, remote-auth pair gate) is carried by dsh-web-app; this bundle only adds tunnel management and the launch contract that admits the tunnel through the /api browser-trust fence.

The host plugin is adapted from @deepseek-ai/dsh-remote-access in the DeepSeek Harness source (MIT), published here under the @froststarinquire scope.

A profile installs this bundle after dsh-web-app in dsh.profile.bundles. Because a bundle patch replaces a whole row's config, the inserted row reads every value from the deployment environment (DSH_REMOTE_ACCESS_*), never literal config. An unconfigured install stays inert: the plugin's provider default is none, so a profile that adds this bundle before owning a tunnel spawns nothing.

The patch also pins the directory picker to the in-app -browse interaction. Through a reverse tunnel the native OS dialog is unavailable, so dsh-web-app's adaptive chooser would leave the remote operator with no way to add a workspace. This bundle disables that chooser and mounts dsh-host-directory-picker-browse plus its dsh-client-ui-directory-picker-browse surface.

Configuration

The row honors the deployment env (all optional; provider defaults to none):

EnvMeaning
DSH_REMOTE_ACCESS_PROVIDERTunnel backend; frp mounts a tunnel through an frpc-compatible client, absent keeps the schema default none (inert). The field is deployment-configurable so other backends can be added
DSH_REMOTE_ACCESS_FRPC_PATHabsolute path to frpc (or compatible); required when provider is frp
DSH_REMOTE_ACCESS_FRP_ARGSfrp fast-start value for -f, i.e. <access-secret>:<tunnel-id>
DSH_REMOTE_ACCESS_CWDworking directory for the tunnel child; defaults to the process cwd
DSH_REMOTE_ACCESS_PUBLIC_URLpublic URL surfaced once the tunnel is up; the plugin's trustedAuthority() canonicalizes it for the trust fence

When provider is frp but frpcPath/frpArgs are absent, the owning plugin refuses to activate loud rather than silently running without a tunnel.

The tunnel's connection address is yours to supply — the plugin never ships a default endpoint. Set the env above to your own provider's public host (DSH_REMOTE_ACCESS_PUBLIC_URL) and launch credential (DSH_REMOTE_ACCESS_FRP_ARGS); without them, an install stays inert.

Launch contract

The tunnel's public authority must reach the /api browser-trust fence at boot — the fence samples trust once when dsh-web-app provides webRuntime, so a runtime plugin cannot retrofit it. Put your own tunnel authority in place of <your-tunnel-host> and launch (and open the remote surface as desired):

dsh --profile web \
  --trusted-host <your-tunnel-host:port> \
  --allow-remote-privileged \
  --remote-auth

--allow-remote-privileged lets the loopback-pinned methods (settings, credentials, native dialogs) accept the trusted authority; --remote-auth enforces the paired-session gate on non-loopback /api. Some tunnel providers (including typical frp edges) are HTTPS-only and return 501 on http://, so open the phone on the https:// public URL.

Known Limitations and Deferred Work

  • The remote surface is not authenticated by this bundle--remote-auth enables the pairing gate in dsh-web-app; without it, the tunnel exposes the harness to anyone who can reach the public authority. Only run on a tunnel you trust.
  • The trust fence is a boot-time snapshot — the tunnel authority must be passed via --trusted-host at launch; it cannot be added after boot from this bundle's runtime.