dsh-tether

DSH Tether

DSH in your pocket: connect to your machine when you have one, run it on the phone when you don't. Remote: across networks, peer to peer, no server to set up, no shared Wi-Fi — if hole-punching fails it falls back to a relay that sees only ciphertext. Local (Android): the DeepSeek Harness runs on the phone itself — install and go, no Termux, no commands.

An independent community project. Not affiliated with, partnered with, authorised by, or endorsed by DeepSeek. No DeepSeek employee or upstream DeepSeek Harness team member is involved in this repository. 中文 · English

Official repository: github.com/zexadev/dsh-tether — releases and issues live here; forks are not maintained by this project. 手机远程使用电脑上的 DeepSeek Harness（dsh）：跨网点对点直连、不用架服务器；Android 还能把 dsh 跑在手机本地。

DSH Tether carries the DeepSeek Harness web interface to your phone over a direct peer-to-peer connection. The agent keeps running on the machine your code lives on, and the phone gets DSH's own full interface — conversations, tool calls, approvals and settings, not a reimplementation of them. Pair once with a 6-digit code; after that the two ends find each other whatever network they are on.

When there is no machine around, the same app can run DSH on the phone itself (Android) — see Local mode. The case it solves

You are not on your machine's network, and you do not want a server in the middle.

Reaching your own dev machine from a phone usually asks for one of two things: both ends on the same LAN, or a relay you deploy, configure and trust. This asks for neither. The two ends hole-punch to each other through iroh, and once they do, nothing passes through a third party; the fallback relay only ever carries ciphertext it cannot read.

If you only use your phone on the same Wi-Fi as your machine, you don't need any of this — a LAN setup is simpler. Compared with similar projects

The two projects most often compared with this one are liguobao/ds-harness-remote and chokwinlee/deepseek-harness-desktop. Going by their READMEs: Download and install The plugin carries a small Rust sidecar that owns the iroh connection, shipped as one package per platform; installing pulls only the one matching your system, with nothing to choose.

The phone build is split by CPU architecture. Any Android phone from the last decade takes arm64; arm is for 32-bit legacy devices, and x86 / x86_64 are for emulators and ChromeOS. Picking the wrong one simply gets refused at install time. Only the arm64 build carries the local-mode runtime; the other three have no such entry.