DSH Go is an Android client for DeepSeek Harness (DSH), the terminal coding agent, and it can either run that agent on the phone itself or take over a DSH session running on your desktop. It is aimed at developers who already work with a command-line coding agent at their desk and want to keep the session moving when they are away from it: on a commute, in a meeting, standing in front of a machine that is not theirs. The app is written in Dart with Flutter, the license is AGPL-3.0, and the project is very new: the repository was created on 2026-10-25 and has gathered roughly 7,200 stars since. A badge in the README reports that Trendshift ranked it first on its all-language daily chart on 2026-10-30.
What it does
The headline trick is that the whole agent lives in the phone. The app installs a Linux environment inside itself, with Ubuntu and Node, so the agent's shell commands and Node tooling have somewhere to run. No root is required, and there is no separate Termux installation to set up first.
Beyond that, the materials describe three things:
- A one-tap switch to another DSH, including the one on your computer, so the same app is both a local agent and a remote console for the agent at home.
- Control of the phone's own screen: the agent reads the screen, then taps and types, action by action.
- An adjustable level of autonomy, where you choose how much the agent decides on its own. The project warns plainly that loosening those limits carries real risk and asks you to read up before you do it.
There is also a cosmetic layer the README leads with: two mascots, Deepy and a whale character the Chinese README calls Jingniang, animate while work is happening, do a flip when a task finishes, and raise a hand when they need your confirmation. Granting the "display over other apps" permission lets them sit on your home screen.
How it works
DSH Go is a Flutter front end around two back ends. In local mode, the bundled Linux userland is the execution environment, which is why Ubuntu and Node are shipped with the app rather than assumed to be on the device. In remote mode, the app is a client that connects to a DSH instance elsewhere and the work happens on that machine.
The intelligence is not in the app either way. DSH Go talks to a model over an API, which is why the key matters (see below). For screen control, the materials state the behaviour (reading, tapping, typing, step by step) but not which Android interface it uses, so treat the mechanism as undocumented here.
Getting started
Requirements: an Android phone running Android 8 or newer, per the badge in the README. Root is not needed. The project does not list memory, chip or storage requirements, so the only published floor is the OS version. There is no iOS build in the materials.
What costs money: the app itself is free and open source under AGPL-3.0, but the model is not included. As the channel's own write-up puts it, you still bring your own model API key, and DSH Go does not provide one, so whatever your model provider charges is your bill. The materials do not mention running a local model on the phone instead, so do not count on it.
The code is at github.com/ccch1mneyyy/dsh-Go. This is not a plain clone and build: it is an Android app, and the README's Android badge points at the repository's latest GitHub release, so that Releases page is where the installable build lives. Installing from there rather than from an app store means letting your phone accept an install from outside the store. The primary README is in Simplified Chinese, with an English translation at README.en.md; support channels listed are a forum at forum.dshtui.com and a QQ group.
When to use it / when not
The main catch is the key: this is a free shell around a paid model, and without an API key you have an app that cannot think. The second catch is age. At the time of writing, the first commit is about ten days old, which is early for software you are going to hand screen-tapping rights to on your main phone.
Use it instead of Termux plus a hand-rolled SSH session when you want the Linux environment, the agent and the remote switch in one app you do not have to assemble. Don't use it if you are on iOS, if you cannot supply a model API key, if your work cannot leave your own machines, or if AGPL-3.0 is a problem for what you plan to build around it.
Take this one seriously if you are an Android user who already lives in a terminal coding agent and keeps hitting the moment where the laptop is shut and the job is not finished: the bundled Linux and the one-tap handoff to your desktop DSH solve exactly that, and nothing else in the materials pretends to do more. Be conservative with the autonomy setting and with screen control until the project has more road behind it, and go in knowing the model bill is yours.