Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL

ZSeven-W/dsh-android

AI Engineering

DeepSeek Harness plugin that streams a live Android emulator or USB device into the conversation and drives it through adb.

355
36
TypeScript
MIT
2 months old

What it does

DSH Android is a plugin for DeepSeek Harness (DSH) that puts a live Android device — an emulator or a USB-connected phone — inside a conversation. The agent gets 20 tools to list devices, boot an emulator, capture the screen, tap/type/swipe, build and install a Gradle project, inspect the UI tree, read logcat, and check processes and memory (tool reference).

A persistent adb exec-out loop runs screencap -p on the device and the host splits the concatenated PNGs into frames itself, so there is no separate stream server or inner port. Frames render in a sidebar panel where you can tap, drag, rotate and press Back / Home / Recents directly on the video. Because the only device identity is the adb serial, emulators, USB phones and ip:port targets follow one code path.

Install and first run

Requirements: Node ≥ 24.11.0, adb from Android SDK platform-tools, and a device with an online adb serial (USB debugging enabled on a phone). OCR tools additionally need a macOS host with Apple's Vision framework.

  1. Install the plugin into the web profile and start DSH:

    dsh plugin --profile web add @zseven-w/dsh-android@latest
    dsh web
    
  2. Ask the agent to list devices (calls android_devices) and pick a serial.

  3. Ask it to stream that serial (calls android_boot); the sidebar panel opens with the live feed. An AVD name instead of a serial boots that emulator first.

  4. Drive the device by tapping on the video, or by asking the agent to open an app, dump the UI tree, OCR the screen, or read logs.

  5. For app work, point android_build_run at a Gradle project path; it runs assembleDebug, installs the debug APK and launches it.

If adb is not found, the error names the three lookup tiers (the ADB env var, PATH, then ANDROID_HOME/ANDROID_SDK_ROOT platform-tools). See the platform-tools download if it is missing entirely.

Constraints

  • Host platforms: all 20 tools work anywhere, but android_find_text, android_tap_text and android_wait_for need the macOS Vision framework; on Linux/Windows they report OCR unavailable unless Tesseract is configured via DSHPLUGIN_ANDROID_OCR_BACKEND and related env vars.
  • Non-ASCII input: adb shell input text is ASCII-only, so CJK/emoji typing is refused unless ADBKeyboard is installed and set as the active IME.
  • Physical devices: android_shutdown cannot power off a phone (adb has no such verb), and frame rates are lower over USB (about 2–5 fps) than on an emulator (about 5–10 fps).
  • Panel needs DSH ≥ 0.1.0-rc.6 with the web bundle; headless profiles still get all 20 tools.
  • Embedded access: the plugin routes are loopback-fenced and HMAC-signed; behind a reverse proxy you must list public hosts in trustedAuthorities. Origin checks are browser protection, not authentication, so only expose those routes behind an authenticating proxy.
  • Licence: MIT.

HotRepo's take

This is a thin-plugin architecture with a deliberate choice to keep one adb code path and stream PNGs in-process from the latest-frame buffer. That buys simplicity and a small attack surface at the cost of frame rate: the README's own numbers are around 8 fps on an Android 14 emulator and 2–5 fps over USB. The roadmap already names the natural upgrade (scrcpy-server plus WebCodecs H.264 behind the pluggable StreamSource seam). For agent-assisted Android testing it is a complete loop — discover, stream, interact, build, install, inspect logs and crashes — and the macOS-only OCR is the main portability gap to plan around. There are no HotRepo rank or growth records for this repository yet, so this assessment rests on the documented architecture and tooling.

Written by AI from the project's README, updated . The project's own docs are the source of truth.

You might also like

  1. ZSeven-W/dsh-iosGives coding agents 22 tools to boot, build, and drive iOS Simulators or USB-connected iPhones, with a live interactive sidebar.TypeScript469
  2. hridaya423/phonedriverMCP server and CLI that let AI agents read and control Android phones and iPhones with a confirmation step before payments.Rust150
  3. phone-harness/mcpA hosted MCP server that lets AI agents control real iPhones and Android emulators in the cloud.Python812
  4. KnifeLemon/DroidlineAutomate and test real Android phones from Python, Node.js, C#, CLI, HTTP or Appium without ADB, USB or root.Go547
  5. ccch1mneyyy/dsh-GoAndroid client for DeepSeek Harness that runs the coding agent on-device or connects to a remote host.Dart19,726