I’ve been building Buddy, a free, open source (Apache 2.0) Android app. You type or say what you want in a floating bubble, and an AI agent reads the screen, taps and types through your apps to do it.
- Your choice of agent: Claude Code, Codex, OpenCode, Antigravity or Grok, running inside the app (Alpine Linux via proot) on your own plan. OpenCode’s free models need no account.
- No root, adb or PC: it reads the screen and taps through the accessibility service.
- Asks first: before anything is sent, posted, bought or deleted. It pauses when you touch the screen and never types passwords or payment details.
- Builds apps: with Linux tools on, it builds real APKs on the phone. This week I drew a maze on a paper towel, took a photo, and it made it a tilt game. The first build crashed on launch; it found the bug and fixed it.
To be upfront:
- What the agent reads on your screen goes to the AI service you pick.
- It’s early (2.2), tested most on a OnePlus 12 with Android 16.
- It’s not on Play (Google rejected the accessibility use), so it’s an APK from GitHub releases, built by GitHub Actions from the source.
Source and releases: github.com/ghorbelhamdi/buddy-android
Happy to answer questions here.
Yeah, 27B only usable if you can fit it entirely in VRAM. Only MoE models are fine to split, like the mentioned Qwen 3.8 Flash Next. Even though it’s large, only the active 6B parameters needs to be located in VRAM, the rest can be in RAM and SSD.
Good call. Qwen3.6 35B-A3B runs fine split between my 8 GB card and RAM, and gets the task right. Flash Next is too big for 32 GB. The latest Buddy (2.2.27) also fixes local models with Codex, which your suggestion helped me find.