wikkd/dsh-remote-access-web#remote-access-web
Reverse tunnel for the DSH Web GUI: exposes a `dsh --profile web` deployment at a public frp URL and switches the directory picker to the in-app browser, so a phone or remote machine can open and manage the workspace.
Listed
2
Remote
Bundle verified
What it does
Reverse tunnel for the DSH Web GUI: exposes a `dsh --profile web` deployment at a public frp URL and switches the directory picker to the in-app browser, so a phone or remote machine can open and manage the workspace.
Best for
- People who need to manage a DSH Web workspace from a phone or remote computer.
- Deployments that already use an frpc-compatible reverse-tunnel service and need a public Web URL.
- Remote workflows that need the in-app directory browser because native folder dialogs are unavailable through a tunnel.
Not ideal for
- Local-only DSH Web use where loopback access and the native directory picker already work.
- Environments without an frpc-compatible client or the required tunnel and environment configuration.
- Deployments unwilling to configure the trusted host, remote privileged access, and remote authentication required by the documented launch contract.
README
dsh-remote-access-web
| English | 中文 |
Source and publishing repository for the DeepSeek Harness remote-access plugin family. It hosts two packages that let a remote device reach a dsh --profile web deployment through a managed reverse tunnel. The tunnel backend is selected by a configurable provider; the shipped driver is the frp provider running an frpc-compatible client.
Packages
| Package | Role |
|---|---|
@froststarinquire/dsh-remote-access |
Reverse-tunnel host plugin (ctx.remoteAccess): manages and keeps alive the outbound tunnel child for the configured provider |
@froststarinquire/dsh-remote-access-web |
Installable profile bundle mounting the tunnel row over dsh-web-app
|
Upstream
The dsh-remote-access host plugin is adapted from the @deepseek-ai/dsh-remote-access plugin in the DeepSeek Harness source (MIT). This repository publishes it under the @froststarinquire scope; it targets the same @deepseek-ai/* peer packages that the official harness ships. The remote-auth pairing plugin and its settings UI are not republished here — they ship with the official dsh-web-app surface.
Status
Both packages are published to npm: @froststarinquire/dsh-remote-access (host plugin) and @froststarinquire/dsh-remote-access-web (bundle). They depend as peers on the released @deepseek-ai/* harness packages (cordis, dsh-subprocess, dsh-invariants). See INSTALL.md for the one-command install and the frpc + environment setup the tunnel needs.
Remote workspace picker
The installable bundle pins the directory-picker to the -browse interaction. dsh-web-app normally uses an adaptive chooser that only offers a native OS dialog on loopback; through a reverse tunnel that dialog is unavailable, so a remote operator would have no way to add a workspace. The bundle disables that chooser and mounts the in-app browse dialog (host backend + client surface) instead.
Install the bundle
From the main DeepSeek Harness installation:
dsh plugin --profile web add @froststarinquire/dsh-remote-access-web
Then launch the web surface, replacing <your-tunnel-host:port> with your own tunnel’s public authority:
dsh --profile web \
--trusted-host <your-tunnel-host:port> \
--allow-remote-privileged \
--remote-auth
See the bundle README for the full launch contract.
AIGC Disclosure
Developed with AI assistance. The code, documentation, and listing copy here were written or revised with a language model, then reviewed by a human maintainer. The dsh-remote-access logic itself derives from upstream MIT code. Review the source before deploying it to an untrusted environment.
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:wikkd/dsh-remote-access-web#path:/packages/bundle/remote-access-web in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.