Back to directory

dsh-mobile

In a curated listMaintenance: Active

pavel-logachev/dsh-mobile

DeepSeek Harness Android app: control your DeepSeek Harness agents from your phone. The agent runs on your PC; a host plugin inside DSH pairs the phone by QR code over Wi-Fi or Tailscale, no cloud. Chats of all projects, live replies, photos and files, steer, agent questions, notifications. Unofficial, MIT.

View on GitHubHomepage
$ dsh plugin add dsh-mobile

19

stars

8

forks

Kotlin

Language

MIT

License

2026-10-04

Created

2026-11-18

Last push

MIT Kotlin Android app plus a DSH host plugin: drive DeepSeek Harness from the phone over Wi‑Fi or Tailscale — cross-project chats, task assignment with attachments, live replies, queue and steer, question answers and best-effort notifications, with the agent and its permissions left on the computer.

DSH integration

Native runtime

Author-claimed

Safety audit

Unaudited

Last verified

2026-11-16

License

MIT

01What can it help you accomplish?

  • Hand a DeepSeek Harness task to the agent from the phone: pick a project and a preset, write the task, attach photos or files, and read the reply as it streams while the agent keeps working on the computer

    A new chat in the chosen project with the task text sent once, the reply rendered live as Markdown with tables and copyable code blocks, and images or files from that reply opened, shared, saved or downloaded

    People who keep a DSH machine running and want to start and follow work from an Android phone on the same Wi‑Fi, over Tailscale, or through their own relay

  • Steer a running turn instead of waiting for it to end: queue an extra message, deliver it at the agent's next step, pull it back out of the queue, or answer a question the agent is blocked on

    A queued message that reaches the agent on its next turn, a steered message delivered at the next step without stopping the current turn, and an answer that is one of the offered options, your own text, or a skip

    Anyone running long agent turns who has to correct course or unblock a question from the phone instead of walking back to the desktop

  • Stop watching the chat and get told when the task is done, failed or waiting for an answer — then pick the conversation back up

    A local notification that opens the matching chat, a final outcome that replaces its waiting alert, and a chat resumed with message search, a per-chat draft, a rename or a model change

    People who start a task and put the phone away, and anyone who would rather not have Google push services carry their task notifications

02How to install into DeepSeek Harness

Prerequisites

  • Windows on the computer with DeepSeek Harness `0.2.0-rc.2`, `0.2.1-alpha.1` or `0.2.1-rc.5` — rc.5 is the main target, rc.4 is unsupported, and DSH itself must run on Node 24
  • Node.js 24.x and OpenSSL 3 on the computer; the companion plugin runs on Node.js
  • Phone: Android 8.0+
  • A reachable address for the computer: home Wi‑Fi, both devices in your Tailscale network, or your own relay on a VPS

Installation steps

  1. 01

    Download the signed APK, the host ZIP and both SHA-256 files from the same release (currently 0.9.3), and do not mix files from different releases

  2. 02

    Compare the two hashes with the release's `.sha256` files — `(Get-FileHash -LiteralPath $zip -Algorithm SHA256).Hash.ToLowerInvariant()` for the host ZIP — and stop on a mismatch

  3. 03

    Extract `tools/install-host.ps1` from the archive and read it, then dry-run `& $installer -ZipPath $zip -Hosts $hosts -WhatIf` and run it without `-WhatIf`, with the computer's LAN or Tailscale address in `-Hosts`

  4. 04

    Activate the plugin with `& $installer -ZipPath $zip -Hosts $hosts -Activate`; the installer does not restart DSH, so a restart is approved separately if needed

  5. 05

    Install the signed APK on the phone: allow Android to install apps from that source, then turn the permission off again

  6. 06

    Check the prepared configuration with `node $cli verify-config --config $config`

  7. 07

    Pair with one command — `node $cli pair --config $config --read all --ttl 300 --qr` for read-only access to all current and future projects, or `node $cli pair --config $config --read all --execute all --ttl 300 --qr` to let the phone run tasks as well

  8. 08

    In the app tap “Scan QR code”, check the computer's address and the certificate fingerprint, then confirm pairing

Verify the integration

  • `node $cli verify-config --config $config` must succeed before you mint an invitation — run it against `$env:LOCALAPPDATA/DSHMobile/host/host.json`
  • Both hashes match the release's `.sha256` files; a mismatch means stop
  • After scanning, the app shows the computer's address and certificate fingerprint, and pairing is confirmed on a match

03DSH integration and capability boundaries

DSH integrationNative runtime

DSH host plugin — the release ships a companion plugin that is mounted inside DeepSeek Harness with the reviewed `install-host.ps1` installer and opens a narrow HTTPS API to the paired Android app over Wi‑Fi, Tailscale or your own relay, with no cloud server. Pairing is a QR invitation minted by the plugin (`node $cli pair --config $config --read all --ttl 300 --qr`), and every app feature shows up only when the host reports the matching capability, e.g. `promptOutcomes` for task notifications

  • Chats from every project

    One list holding chats from all DSH projects, searchable and filterable by project, following the DSH sidebar without re-pairing

  • Task assignment with photos and files

    a project, a preset and the task text, plus camera shots, photos from the system photo picker or files from the system file picker→A new chat in the chosen project with the task text sent once, carrying up to 20 attachments totalling 200 MiB with each file up to 20 MiB

    the app creates a chat in the chosen project and sends the task text onceuploads start as soon as you pick the files, and files are handed to the DSH attachment store at the moment of sendingunsent uploads expire on the computer after 10 minutes and never reach DSH
  • Live reply view

    The streaming reply as Markdown with tables and code blocks that have a copy button, images in place with a full-screen viewer to zoom, share or save, files downloadable up to 20 MiB, and service events collapsed into one “Agent activity” line

  • Queue and steer

    a message typed while the agent is still working→The message queued for the agent's next turn, delivered at its next step when you use Steer, or removed from the queue again

    a steered message arrives at the agent's next step without stopping the current turna queued message reaches the agent on its next turn
  • Answering agent questions and stopping a run

    One or more options chosen, a hand-written answer or a skipped question, with the recommended option marked but never preselected; Stop asks for confirmation before ending the run

    approvals of agent actions are not part of this flow — they stay on the computera stop you make yourself clears the waiting notification silently, without an error alert
  • Task notifications

    one local switch in the app, with a host that publishes `promptOutcomes`→Completion, failure and needs-answer alerts for phone-started tasks, each opening the matching chat and a final outcome replacing its waiting alert

    only phone-started tasks are watched; desktop-started tasks are not automatically watchednotification sound is controlled by Android channels, not by the appno idle service or permanent connection notification runs in the background

04Who is it for? When not to use it?

Good for

  • People who keep a DSH machine running and want to start and follow work from an Android phone on the same Wi‑Fi, over Tailscale, or through their own relay
  • Anyone running long agent turns who has to correct course or unblock a question from the phone instead of walking back to the desktop
  • People who start a task and put the phone away, and anyone who would rather not have Google push services carry their task notifications

Not for

  • The computer and DSH must stay on: the phone runs no agent, one pairing targets one computer, and the project list only considers the first 100 registered projects.
  • Pairing is a real grant, not a sandbox: the plugin runs inside DSH with DSH's own permissions, project filtering is not a sandbox, and the QR invitation is single-use and valid for no more than 15 minutes — so only trusted devices should get the right to run tasks.
  • It is deliberately a native subset, not desktop parity: plugin and skill management is not exposed from the phone, and approvals of agent actions still have to happen on the desktop, separate from answerable agent questions.
  • Notifications are best effort with no FCM or UnifiedPush: Doze, battery saving, an offline device, the 24-hour expiry or eviction from the 32-watch bound can prevent delivery, and after a force-stop the app has to be launched by hand.

05Compatibility, maintenance and safety notes

  • The computer and DSH must stay on: the phone runs no agent, one pairing targets one computer, and the project list only considers the first 100 registered projects.
  • Pairing is a real grant, not a sandbox: the plugin runs inside DSH with DSH's own permissions, project filtering is not a sandbox, and the QR invitation is single-use and valid for no more than 15 minutes — so only trusted devices should get the right to run tasks.
  • It is deliberately a native subset, not desktop parity: plugin and skill management is not exposed from the phone, and approvals of agent actions still have to happen on the desktop, separate from answerable agent questions.
  • Notifications are best effort with no FCM or UnifiedPush: Doze, battery saving, an offline device, the 24-hour expiry or eviction from the 32-watch bound can prevent delivery, and after a force-stop the app has to be launched by hand.
2026-10-042026-11-13v0.9.3

MIT · latest release v0.9.3 (2026-11-08T08:33:47Z) · Android client + DSH host plugin, no shared public relay

06Frequently asked questions

How does DSH Mobile install into DeepSeek Harness?

The phone app and the host side are two halves of one release. On the computer you extract `tools/install-host.ps1` from the host ZIP, dry-run `& $installer -ZipPath $zip -Hosts $hosts -WhatIf`, run it again without `-WhatIf`, and activate with `& $installer -ZipPath $zip -Hosts $hosts -Activate`; on the phone you install the signed APK. The README documents no marketplace or npm install command — the release archive and that installer are the install path, and the app and the plugin have to come from the same release.

Which DSH, Node.js and Android versions does it need?

On the computer: Windows, DeepSeek Harness `0.2.0-rc.2`, `0.2.1-alpha.1` or `0.2.1-rc.5`, Node.js 24.x and OpenSSL 3. rc.5 is the main target and rc.4 is unsupported; DSH itself must run on Node 24, not just a suitable executable on `PATH`. On the phone: Android 8.0+.

Does the phone run the agent or receive my model credentials?

No. Models, tools and subscriptions stay on the computer and DSH Mobile has no cloud server, so the phone is only a client and the agent keeps working after you close the app. Provider keys are not sent to the phone: pairing data sits in the Android Keystore and is excluded from backups, and the plugin's private files on Windows are accessible only to the owner of the user account.

What can the phone do inside a DSH session?

Open chats from all projects, assign a task with photos and files in one message (up to 20 attachments, 200 MiB total, 20 MiB per file), read the reply live, queue a message or steer it in at the agent's next step, answer the agent's questions and get completion or needs-answer notifications. Every feature appears only when the host reports the matching capability, and approvals of agent actions still happen on the desktop.

What happens if the phone loses the connection during a task?

A dropped connection never proves the task was not delivered. The app retries at most three times with the same requestId and only when the transport proves the request headers were never sent; it never resends automatically after admission, and for `uncertain` the README says to inspect DSH first. Notifications are best effort without FCM/UnifiedPush, so a pending task can also go quiet under Doze or battery saving.

08Data and sources

  • Author-claimedgithub.comc549813db2ff…

    A companion plugin is installed on the computer.

  • Author-claimedgithub.comc549813db2ff…

    Companion plugin inside DSH

  • Author-claimedgithub.comc549813db2ff…

    Features are available only when the host reports their capability.

This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-11-16. Found an error? Submit a correction.

🏆

Best DeepSeek Harness Plugins

Twelve plugins worth installing first — picked from the whole catalog, across every category.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.