DSH Mobile Suite

English | 简体中文

Open the DeepSeek Harness Web UI on your computer from an Android phone, then create tasks and submit instructions through the familiar DSH interface.

Unofficial community project: this project is independently developed and maintained by the community. It is not reviewed, endorsed, or supported by DeepSeek. The current release is an MVP and does not yet provide end-to-end encryption.

DeepSeek Harness community post: Show Your Plugins! #2520. This is a community discovery entry, not an official review or endorsement.

Components

This repository pins three independently developed and released open-source components as Git submodules:

The phone never connects directly to the computer. The plugin opens only an outbound WSS connection to the Relay, while DSH remains bound to 127.0.0.1:3080.

Default public Relay: https://relay.dshmobile.online

Install and use

Download these files from the latest release:

• dsh-mobile-android.apk: signed Android installer
• dsh-mobile-plugin.tgz: prebuilt DSH plugin package
• dsh-relay-v*.tar.gz: Relay source package for private deployment
• SHA256SUMS: SHA-256 checksums for every release asset

Verify the downloaded files:

shasum -a 256 -c SHA256SUMS

Install the pinned plugin directly from GitHub, then start DSH. This path does not require a global DSH installation, a source checkout, or a local file path:

npx @deepseek-ai/dsh plugin --profile web add "github:april-jk/dsh-mobile-plugin#v0.1.2"
npx @deepseek-ai/dsh web

Install dsh-mobile-android.apk on your Android device. Android may ask you to allow the browser or file manager to install unknown apps. The application ID is io.github.apriljk.dshremote.

Pair and run remote tasks

1. Register or log in from the mobile app.
2. On the computer, open Settings > Remote Access in DSH and create a six-digit pairing code or QR code.
3. Tap + in the mobile device list, then scan the QR code or enter the six-digit code.
4. Select the online computer to open its normal DSH Web UI.
5. Create a task and submit instructions through the existing DSH interface.

The plugin follows the DSH Web process lifecycle and does not need a separate background process. The phone shows the computer as offline when the computer or DSH is stopped, or when the plugin is disconnected from the Relay.

Deploy a private Relay

Download and extract dsh-relay-v*.tar.gz from the release, then run:

cp .env.example .env
# Edit .env and replace JWT_SECRET with a long random value.
docker compose up -d --build
curl http://127.0.0.1:8787/health

For public access, put an HTTPS reverse proxy in front of port 8787 and back up the SQLite data under /data. The MVP Relay must run as a single instance.

The computer and phone must use the same Relay:

DSH_RELAY=https://relay.example.com npx @deepseek-ai/dsh web

On the mobile login screen, tap Relay, or open Settings > Relay Server after logging in, and enter the same HTTPS origin. Changing the Relay logs out the current account because accounts and tokens are isolated between Relay instances.

See the Relay README for all environment variables and resource limits.

Security boundaries

• Public traffic must use HTTPS/WSS; the computer never opens a public listening port.
• The mobile app receives account tokens and short-lived web tickets, never the computer's device credential.
• The Relay does not persist DSH HTTP/WebSocket request or response bodies. The MVP has no application-level end-to-end encryption, so the Relay process can see traffic while forwarding it.
• The Relay stores accounts, devices, pairing state, and bounded access-log metadata. Account deletion, a privacy policy, and related compliance work are still required before app-store distribution.

Report security issues privately as described in SECURITY.md. Do not disclose exploitable details in a public issue.

Development

git clone --recurse-submodules https://github.com/april-jk/dsh-mobile-suite.git
cd dsh-mobile-suite
git submodule update --init --recursive

Commit component code in its own repository. This repository maintains cross-component documentation, the unified release workflow, and tested component revisions. See CONTRIBUTING.md to contribute.

License

The suite and all three components use the MIT License.