Authorization notice. DSH Android is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forAn Android developer who wants to test a Gradle project on an emulator or USB phone without switching windows.
The problemBuilding, installing, and launching an Android app by hand takes several separate commands, and checking the result means picking up the device.
The outcomeThe app is built, installed, and launched on the chosen device, and the live panel shows the result.
What you need first
- A DeepSeek Harness (DSH) host, tested by the author with DSH 0.1.5-rc.1
- adb available on the machine so the plugin can resolve it
- A running Android emulator or a USB-connected Android phone
- For builds: a Gradle project that has ./gradlew
Steps
- Run
adb devices -lthrough android_devices and note the serial of the online emulator or phone. - Call android_boot with that serial so the live stream appears in the panel.
- Call android_build_run with the Gradle project path, which runs
./gradlew assembleDebug, thenadb install -r, then launches the app. - Call android_screenshot to confirm the first screen, and use android_interact to tap through it.
- If the build fails, read the Gradle error tail in the result, then call android_logs in snapshot mode with bundle_id set to the package name.
Prompt for your agent
Using the dsh-android plugin, call android_devices, pick the online serial, call android_boot with it, then call android_build_run with projectPath set to <path to the Gradle project>. Expected output: a result showing the debug APK installed and the app launched, plus a screenshot path. Verify that the install and launch both succeeded before reporting done.
Caveat. The first full Gradle build takes minutes, and the plugin only works when adb can be resolved on the machine.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page