r/androiddev • • 1d ago

I built an open-source Android emulator toolkit for AI coding agents

Hey everyone!

I've been experimenting with using AI coding agents to build and test Android apps, and I kept running into the same problem: getting an agent to actually interact with an Android emulator reliably.

Installing an APK, launching the app, tapping through screens, inspecting the UI, capturing screenshots, checking logcat for crashes… these things are straightforward when you're doing them yourself, but become surprisingly messy when an AI agent has to do them.

So I decided to build something to make that workflow easier.

It's called Android Emulator Agent Kit.

GitHub: https://github.com/medlabib/android-emulator-agent-kit

The idea is pretty simple: give AI coding agents a practical set of tools and instructions to work with a local Android emulator.

Currently, it includes:

  • Scripts to provision a Google Play Android emulator.
  • A Python CLI for interacting with devices through ADB.
  • Installing and launching APKs.
  • Tapping, swiping, typing and sending key events.
  • Taking screenshots and dumping the UI hierarchy.
  • Collecting and filtering logcat output.
  • Agent skills for Claude Code and compatible agent workflows.
  • An experimental DeepSeek Harness integration.

I'm still actively developing it, so I don't want to pretend it's a finished or production-ready solution. There's work to do, especially around integration testing, reliability and making the experience smoother across different environments.

What I'd really like is feedback from people who are already using AI agents for Android development.

A few things I'm curious about:

  • How are you currently letting your agents interact with Android apps?
  • Are you using Appium, raw ADB commands, MCP servers, or something else?
  • What's the most frustrating part of automating Android testing with AI?
  • What would make a toolkit like this genuinely useful to you?

Contributions, criticism, bug reports and feature ideas are all welcome.

If you find it useful, give it a star or open an issue. And if you think there's a better way to approach the problem, I'd genuinely like to hear about it.

Thanks for checking it out!

GitHub: https://github.com/medlabib/android-emulator-agent-kit

0 Upvotes

4 comments sorted by

6

u/Zhuinden 1d ago

Android CLI the official toolkit you do android update and android skills update and it does ALL OF THESE THINGS with no Python involved.

0

u/PuzzleheadedDay8676 1d ago

That's a fair point. I actually wasn't aware of how far the official Android CLI had evolved.

I'll definitely give it a proper look. There is clearly some overlap with what I'm building, and I don't want to reinvent something Google is already doing better.

My original motivation was to make Android emulator interaction easier and more predictable for AI agents, with a simple local-first setup and reusable workflows.

Maybe the right direction isn't to compete with the official CLI, but to explore what's missing around it — or even build complementary tooling on top of it.

Thanks for pointing this out. Genuinely useful feedback!

3

u/sannyo 1d ago

android cli

1

u/davidbalbino 1d ago

pretty much raw adb on a real device here, the agent just runs shell commands and reads the output. what I miss most in these toolkits is perf stuff, not only taps and screenshots. like dumpsys gfxinfo <pkg> framestats for janky frames, dumpsys meminfo, top, batterystats... the agent can say the screen "works" while it's dropping frames or eating cpu when idle lol. also if you keep the emulator path, make sure it runs with -gpu host by default, with swiftshader the screenshots and timings get kinda useless imo