Phone
Sign in, scan the encrypted pairing QR code, then choose an online computer.
Open source Android remoteDeepSeek Harness on your phone
Pair once, open your local Harness, and submit normal tasks from Android through the familiar Web UI.
Unofficial community project. Independently developed and not reviewed, endorsed, or supported by DeepSeek.
Remote access without a public computer port
The phone, Relay, and computer each have one clear job. Your local DSH listener stays local.
Computer
The plugin follows the DSH Web process. DSH stays bound to 127.0.0.1:3080.
Relay
Routes authenticated opaque frames without receiving the DSH content key.
Pair. Open. Run.
The remote flow stays inside the interfaces you already use.
- 1
Install and start
Install the signed Android APK and the pinned DSH plugin, then start DSH Web.
- 2
Pair the phone
Open Settings > Remote Access, then scan the encrypted QR code.
- 3
Use the normal Harness UI
Choose the computer, create a task, submit instructions, and follow progress in real time.
The real Harness workspace, fitted to mobile
Keep the normal workspace picker, mode, model, task composer, live reasoning status, elapsed time, and stop control.
See how remote sessions workOutbound-only from the computer
The Companion opens an outbound WSS connection. It does not create a public listener or send the device token to the phone.
Android phone
HTTPS/WSS Relay
Local DSH
127.0.0.1:3080
Version 0.1.4 encrypts DSH session content end to end; traffic metadata remains visible to the Relay.
Read the security modelHosted by default. Self-hosted when you need it.
Public builds can switch to a compatible private Relay without recompiling the app.
Hosted Relay
Start quickly with relay.dshmobile.online. The phone and computer use the same account boundary.
https://relay.dshmobile.onlinePrivate Relay
Deploy the MIT-licensed Relay behind HTTPS, persist its data, and point both ends to your origin.
Deploy a private RelayQuestions before you pair
Straight answers about compatibility, traffic, and project status.
Is DSH Mobile an official DeepSeek product?
No. It is an independently developed open-source community project. DeepSeek has not reviewed, endorsed, or supported it.
Does it expose DSH directly to the internet?
No. DSH remains on 127.0.0.1:3080. The computer-side plugin opens only an outbound WSS connection to the configured Relay.
Can I use my own Relay server?
Yes. Deploy the open-source Relay behind HTTPS, then configure the same origin in the mobile app and before starting DSH.
Is Relay traffic end-to-end encrypted?
Yes for DSH session content in version 0.1.4. Mobile and Companion encrypt HTTP, SSE, and WebSocket envelopes; the Relay still sees account/device associations, timing, and ciphertext sizes.
Which mobile platforms are available?
The current public release provides a signed Android APK for Android 8.0 or newer. The Flutter source also targets iOS 14 or newer.
Does the phone receive the computer device token?
No. The mobile client uses account access tokens and short-lived WebView tickets. The device credential stays on the computer.
Does the Relay save my Harness tasks?
It does not persist forwarded HTTP or WebSocket bodies. It stores accounts, devices, pairing state, and bounded access metadata.
Put your local Harness within reach
Download the signed Android build, verify its checksum, and pair it from DSH settings.