DSH Mobile

DeepSeek Harness runs on the PC and works on the files of the PC. DSH Mobile adds the two pieces you need to carry it with you: a plugin, which opens a small authenticated HTTP server on the harness, and a native Android app, which talks to it. The phone speaks directly to the PC — on your home Wi-Fi or inside the Tailscale network — and there is no service of ours in between.

The plugin does not touch the Web GUI of the harness: it listens on a port of its own, with a different token for each paired phone, and turns sessions, chats, photos, files, approvals, questions and access levels into a few REST routes. The app is not a web page in a frame: it is Kotlin and Jetpack Compose, and it draws the transcript, the markdown, the diffs and the tool cards itself.

What you write from the phone is the conversation you find on the desktop: same agent, same history, same files. If a chat is open on the PC, the phone tells you so instead of fighting over the turn.

Install the plugin in the profile of the harness and restart it: the log prints the pairing code, which lives until it is used. In the app you type three things — the address of the PC, the code and the name of the phone — and from then on that phone has a token of its own, which you revoke by emptying the list of devices on the PC.

On the PC the firewall has to be convinced once, for the port of the plugin and for private networks only. On the phone no account is needed: a device is a token, and the tokens sit in a file on the PC that only its user can read.

Pending requests live in memory: once the turn is over, an approval left on the phone can no longer decide anything.

What is worth knowing before you install it.

Do I need an account, or a service in between?

No. The phone opens a direct connection to the PC: no server of ours, no cloud. Pairing happens once, with the code the harness prints at startup, and from then on each phone has its own token.

What can the phone do on the PC?

What the harness can do: read and write in the chats, approve the use of a tool, answer a question of the agent and change the access level of the chat, up to Full access — which takes the permission requests away. That is why the listener has to stay on the home network or on Tailscale, and why, when a phone is lost, you empty the list of devices and restart the harness.

Does it work away from home?

Yes, with Tailscale on the PC and on the phone: the address to type in the app is the one of the PC on the Tailscale network, 100.x.x.x. Otherwise you stay on the home Wi-Fi, which is the normal case.

Which phones does it run on?

Android 8.0 or later. The phone has to be able to open a connection to the port of the plugin on the PC: on the Windows firewall it has to be allowed once, for private networks.

Why is the APK signed with a test key?

Because it is a build to install by hand, not one for a store: a debug key is public by definition, and it makes the APK installable with no secret to look after. Anyone who wants to sign updates with a key of their own finds the procedure in the README of the project.

Which languages?

Italian and English, following the language of the phone. The themes are two, light and dark, with “System” choosing for you.