Hah23255 Adb Android Control
hah23255-adb-android-control is a Claude Code plugin for the Build phase that gives your agent comprehensive Android device control through ADB.
by hah23255 · github.com/hah23255/adb-android-control
Let Claude Code drive a real Android phone or emulator over ADB for installs, UI taps, screenshots, logcat, and scrcpy-style mirroring while you build or debug mobile flows.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install hah23255-adb-android-control@hah23255/adb-android-controlBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:hah23255/adb-android-control") and the paste-ready config with skillselion.get_install_config("plugin:hah23255/adb-android-control").
What it does
hah23255-adb-android-control is a Claude Code plugin that turns the Android Debug Bridge into an agent-operable toolkit for solo builders shipping mobile apps or agent-driven QA. Instead of context-switching to Android Studio or manual adb one-liners, you describe goals—reproduce a crash, capture a screenshot, install a debug APK, or scroll through onboarding—and Claude executes structured device operations against a connected phone, tablet, or emulator. The plugin emphasizes comprehensive coverage: connection management, package and activity control, input simulation, file push/pull, log viewing, and optional mirroring/recording paths aligned with common scrcpy-style workflows. It fits indie developers who iterate quickly on Android UX, automation authors who need repeatable device scripts, and anyone validating agent behavior on real hardware. Complexity is intermediate because you need adb on PATH, USB or wireless debugging enabled, and basic Android security model awareness. It is a task integration plugin, not a methodology skill: one phase, one job—make the device an extension of the coding agent during build and ship cycles.
Highlights
- Full ADB command surface: connect, shell, getprop, dumpsys, logcat, and wireless debugging
- App lifecycle: install, uninstall, start activities, intents, broadcasts, and monkey stress runs
- Input simulation: tap, swipe, keyevent, sendevent, and text entry for UI automation
- Capture and mirror: screenshots, screen record, scrcpy-oriented mirroring workflows
- Device health: battery, memory, storage, and settings inspection via dumpsys and getprop
Why builders use it
Debugging and automating Android on a physical device means leaving the agent chat for adb recipes, Studio, and brittle shell scripts.
After you add the plugin, Claude can run installs, UI actions, logs, and captures on a connected device from the same session where you edit code.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 81 stars, 0 votes.
FAQ
Who is hah23255-adb-android-control for?
Android-focused solo builders and agent users who need install, input, logcat, and screen capture from Claude Code without hand-rolling every adb command.
When should I use hah23255-adb-android-control?
Use it while integrating or testing mobile features—reproducing bugs, validating builds, automating taps, or pulling diagnostics during build and ship testing.
How do I add hah23255-adb-android-control to my agent?
Install the plugin from the hah23255/adb-android-control Claude Code plugin bundle, ensure adb is installed and your device authorizes debugging, then invoke Android control tasks from your Claude Code session.
Comments
Share how you use hah23255-adb-android-control, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.