dsh-remote-public: A DSH plugin for Remote-Controlling DeepSeek Harness from Android

What Does It Do?

DSH Remote is a DSH plugin for DeepSeek Harness that lets you control DSH running on your PC from a native Android app. It solves the problem of being unable to check sessions or send instructions once you step away from the computer, connecting directly to DSH's built-in HTTP API and WebSocket gateway with Kotlin/Compose rather than wrapping a WebView. Its core capabilities cover three connection modes, session list management, streaming chat, and model switching, plus a one-click connect script.

Core Features

• Three connection modes: LAN, ngrok tunnel, and custom addresses, with the address and credentials saved locally after the first entry.
• Session list management: search, sort by recent update or manually, and filter by archive state, showing the latest 10 sessions by default and expanding 5 more at a time.
• Session actions: long-press a session to rename it or archive and unarchive it.
• Chat experience: send messages, receive token-by-token streaming replies, and interrupt at any time, with paged history and local caching that shows the last content before syncing.
• Model selection: browse a grouped catalog and switch models; the permission mode can only be read for now because DSH does not yet expose a remote switching interface.
• One-click connect script: double-click it on the PC to start the bridge, issue a 30-day cookie, try to open a public tunnel, and print the results.

How to Use This Plugin?

Double-click the connect script shipped with the app on your PC; it starts the bridge, issues a 30-day cookie, tries to open a public tunnel, and prints the DSH address and cookie while also writing them to a file in the same folder. Then pick the custom profile in the app, paste the address and cookie into their fields, and tap connect. Public access is attempted in order of ngrok, a free cloudflared tunnel, and LAN only, with the LAN address always available; for a stable domain, register a free ngrok account and configure it once. Keep the script window open on the PC, since closing it disconnects the phone, and run it again next time to copy the new address and cookie.

How to Troubleshoot This Plugin?

A 403 response usually means the Host was not rewritten and DSH's trust fence blocked the request, so follow the official instructions to have the bridge rewrite the Host to the value DSH accepts. If every API call returns 401, the tunnel likely has Basic Auth added on top; the app authenticates with DSH's signed cookie, so remove that extra layer. Occasional disconnects are commonly caused by free tunnel quotas or connection limits, so switch to a paid plan or use cloudflared instead.