@wangzan101's open-source on-device Android Phone Agent, Mika, operates apps on a background virtual screen while you keep using the phone
Wang Zan (@wangzan101) open-sourced Mika (Apache-2.0, thousands of stars at launch, latest Release 0.1.33): a Phone Agent that lives on your Android phone. After one sentence it opens apps, taps, types and scrolls on a separate background screen (WeChat messages, group summaries, Xiaohongshu digests, job-site greets, built-in browser shopping…) while you keep using the main display; logins, OTP and payments are handed to you. No required root, no always-on PC; models use your API key or a ChatGPT / xAI / OpenRouter sign-in—the project says there is no Mika server. App control needs Android 12+ (14+ recommended) and a one-time wireless-debugging pair. We cloned commit ebb0e44, read the EN/ZH READMEs, setup guide and privacy notes, and confirmed Releases ship an APK; we had no Android device, installed no APK, and ran no end-to-end model task.
Visit site Mika (wangzan101/Mika) ↗- Pricing
- Freemium
- Region
- Global
- Where it's from
- Chinese community
- Added
- Nov 2, 2026
- Tested on
- Nov 2, 2026
- Version we used
- wangzan101/Mika commit ebb0e44 / Release v0.1.33 (APK not installed)
- Categories
- Automation & AgentsProductivity
- Original author
- 王赞 @wangzan101 ↗
- Our test
- Partly tested
- Cost / time
- APK and source are Apache-2.0 free. Model cost follows your provider (DeepSeek/Qwen/Kimi or Anthropic/OpenAI/OpenRouter); ChatGPT / xAI sign-in rides that subscription.
The task
On a spare or daily Android phone, use natural language so an agent drives already-signed-in apps and sites (summarize chats, batch greets, filter products) while you still use the phone.
Steps
- Chat/web/files need Android 11+; app control needs Android 12+ (14+ recommended so the background screen has its own focus). Linux sandbox needs arm64.
- Install the latest APK from GitHub Releases (0.1.33 when we checked).
- Settings › Model: pick a preset (DeepSeek, Qwen, Kimi, OpenRouter, Anthropic…) and paste a key, or sign in with ChatGPT / xAI / OpenRouter.
- For app control: run the in-app "Set up phone control" wizard—developer options, USB debugging, wireless-debugging pair (~3–5 minutes on-device; some OEMs need USB from a PC—see the setup guide).
- Start with low-risk prompts (alarms, weather); keep default Ask mode for anything that spends money. A computer agent can also follow `docs/install-with-agent.en.md`.
- Optional: run the ~12-check compatibility self-test; from a PC you can dispatch work over CLI + Skill or MCP.
Prompt
Summarize today's chat in my Family WeChat group and list the points back to me. Do not send any message and do not open payment screens.
What the author says
@wangzan101: a real Phone Agent on your Android phone; reuses existing logins, no extra OAuth, no root, no always-on PC; works on a background screen while you use yours; any app, built-in browser use, floating capsule, on-device Linux sandbox. Demos cover WeChat, Xiaohongshu, job apps, carts. README stresses no Mika server—data goes only to your model provider; automation may break third-party ToS, so use Ask mode for anything important.
Our test
Cloned wangzan101/Mika commit ebb0e44; read README.md / docs/readme/README.zh-CN.md, setup-guide, disclaimer and models docs; confirmed via GitHub API that the latest release was v0.1.33 (2026-11-01). No Android device, no APK install, no model config, no wireless-debugging pair.
What we found when we tried it:Repo includes app/core/tools/eval and multilingual docs; the setup guide walks wireless debugging as a checklist, allows skipping accessibility, and states payment screens return control to you. Releases expose an APK and version tag. That matches the launch post—but background-screen stability, OEM quirks and real app success rates were not verified by us.
How to get in
Docs in ZH/EN/JA/KO/ES; APK on GitHub Releases. Works with domestic or international model providers. No iOS build.
Who it suits
People with an Android phone (ideally a spare) who want repetitive app chores handed to an agent and can accept wireless debugging plus third-party ToS risk.
Pitfalls
- No iOS: docs say it depends on Android's background virtual display / accessibility and wireless debugging.
- Some OEMs hide wireless debugging or turn it off after reboot/Wi-Fi changes; re-pair via the wizard or start the helper over USB from a PC.
- Payment and password screens often block capture, so Mika stops and hands control to you.
- Automating WeChat, job apps or shops may break platform ToS and risk mis-sends/orders—stay in Ask mode and try on low-stakes accounts first.
- We only reviewed source and docs—no device install or live task—so OEM quirks are unverified by us.
More in this category
- Scan a skill before installing, then read the flagged linesCodingSkillSpectoruvFree; static scan needs no model● Tested by usChina
- Isolate an always-on agent on its own machine, then red-team itAutomation & AgentsOpenClawClaude CodeOllama$20/mo Ollama Cloud + a Claude plan○ Not tested by usOverseas
- A to-do list beside your agents, one AI chat per taskProductivityToday BoardcmuxClaude CodeFree, open source; needs macOS + cmux◐ Partly testedChina
- Give your agent 300 search sourcesResearchArgoClaude CodeCodexFree; works without API keys◐ Partly testedChina
- Learn a website task once, replay it with no model callsAutomation & AgentsDejoClaude CodePlaywrightFree; needs Python 3.11+◐ Partly testedOverseas