Mika: A No-Root PhoneAgent That Operates Your Android Apps on a Background Screen
Android automation has moved past the root-or-ADB threshold: wireless-debugging pairing gets an on-device agent running with just an APK and one-time setup. For individual developers and QA testers, that makes end-to-end UI automation on a personal device practical without a controlled environment, and the screen-reading model reduces the need for per-app scripts.
Mika is an open-source, Kotlin-based PhoneAgent that automates installed apps on Android via a separate background screen. It pairs once through wireless debugging, eliminating the need for root or a tethered computer. The agent reads the screen like a human, taps, types, and scrolls through whatever you ask: summarizing WeChat chats, tracking a Xiaohongshu blogger, greeting jobs on BOSS Zhipin, or adding a charger to your cart and stopping before checkout. It uses your own model credentials (DeepSeek, Tongyi, Kimi, Zhipu, Volcano Ark, ChatGPT, or OpenRouter) and keeps keys and conversation records encrypted on the device, with no Mika server involved.
The project surfaced on GitHub in late October 2026 and passed 8.6k stars within three weeks, topping trendshift's Kotlin repository daily and weekly charts. Setup is three steps: install the APK, pick a model provider, and pair wireless debugging (skippable if you only need chat, web, or files). Beyond app control, it packs a desktop browser with persistent login, a local Linux sandbox for Python/Node/shell, scheduled and conditional tasks, and a floating capsule for quick screen or voice queries. Default Ask mode requires confirmation before any purchase; a fully autonomous mode exists for the rest.
Caveats matter: automations may violate third-party terms, payment and password pages are unreadable because the OS blocks screenshots, and wireless debugging turns off after Wi-Fi changes or reboots (the agent re-enables it, or you re-pair). A compatibility self-check runs twelve checks in one minute.
Wireless debugging pairing is a genuinely lower-friction path to phone automation than root or USB ADB, because it keeps the device untethered and requires no special developer account; that's the single design choice that makes an APK-only install credible.
The screen-reading approach with a small curated knowledge base for 36 apps and 31 websites is more scalable than per-app scripting, and the project's star growth suggests the market values that tradeoff, even if it means some third-party apps may be affected by UI changes.
The explicit disclaimer and the system-level screenshot restriction on payment/password pages draw the boundary for what an on-device agent can safely do; any implementation must hand control back for financial flows, which is a real constraint, not a bug.
The project's pace of updates, at v0.1.43 within three weeks, indicates a solo developer shipping fast; that momentum fuels adoption but also leaves long-term maintenance and security assurance open questions.
Sir, this must burn through quite a few tokens.