mylea1/phongent
AI EngineeringControls multiple Android device agents from an iOS or Android master device with natural-language tasks and live screens.
What it is
phongent is a multi-device agent coordination project built on top of the upstream Mika project. A master device — either an iPhone or an Android phone — connects to multiple Android execution devices over the local network, dispatches tasks in natural language, and collects progress, messages, and live screens in one place. Android devices can act as both master and local executor; iOS is limited to the master role. The README's role matrix makes this split explicit: iOS supports connecting, assigning tasks, viewing results, and taking over live screens, but not executing app operations on itself, while Android supports all of these multi-device task distribution.
The project fits users who already run phone-automation agents and need to drive several devices at once — for example, running different content-generation or browsing tasks per device and reviewing notifications centrally.
Core capabilities
Tasks can target all connected devices, a named group, or a single device. The master's task model can also decide which device receives a sub-task. Devices can be organized into groups with batch moves, group-level task dispatch, and per-device overrides within a group; grouping state lives on the master and does not sync to other masters. A live small-window view shows the Android virtual screen and accepts taps, swipes, and text input for manual takeover, enabled by default and configurable. Notifications from managed devices are collected by device, app, and source, and can be answered through the target device's agent core features.
Quick start
- Install the project build. On Android, install the latest APK; on iOS, build and sign through Xcode. The README warns against substituting the upstream project's APK because it may lack the multi-device control interfaces.
- Configure the Android executor: model settings and phone-operation settings, granting accessibility, notification-reading, and other permissions as each feature requires. The underlying phone-operation settings are documented in the setup guide, where some names still follow upstream.
- Put master and executor on the same LAN, keep the Android service running, then pick a device on the Devices page or use one-tap connect. The Android side must approve the first connection; authorized devices reconnect automatically.
- Configure the task-dispatch model in the master settings; account sign-in is completed on the corresponding device.
- On the agent page, choose all devices, a group, or one device, enter the task, and inspect progress and results per device.
Build requirements
Android builds require JDK 17 and the Android SDK (currently compileSdk 36); the minimum install target is Android 11, though specific phone-operation capabilities also depend on system version and permissions. Build with ./gradlew :app:assembleDebug; output lands in app/build/outputs/apk/debug/. The README advises confirming the build is signed with your own development certificate before installing. iOS requires macOS, an Xcode version supporting the project SDK, and a minimum deployment target of iOS 17; open ios/MikaRemote.xcodeproj, select the MikaRemote scheme, and choose your own development team for signing. Model keys, account credentials, and local signing material should not be committed to source build and development.
License and provenance
The code is Apache-2.0 licensed and derived from Mika, with cross-platform master control and multi-device coordination added license. Third-party assets such as avatars carry their own licenses, listed in the third-party notices.
HotRepo's take
The README and repository structure are unusually concrete for a project of this kind: there are separate directories for the Android app, agent core, iOS master, emulator tooling, and docs, plus exact build commands and a role matrix. That is a meaningful signal against the usual pattern of vague download pages. What the material does not establish is the provenance of the prebuilt APK — no signing details or author identity beyond a social handle — so the binary is the part to treat with caution, not the source layout. This repository has no HotRepo daily ranking, snapshot, or discussion record yet, so no trend claim can be made from site data.
Written by AI from the project's README, updated . The project's own docs are the source of truth.
You might also like
- droidrun/mobilerunAn LLM-agnostic framework that lets AI agents inspect, tap, swipe, and type on real Android and iOS devices via CLI or Python.
- moonoops/DroyAn on-device Android agent that plans tasks and controls apps through authorization-scoped phone tools.
- zai-org/Open-AutoGLMA phone-use agent framework that drives Android and HarmonyOS devices from natural-language instructions via a vision-language model.
- kevinbadi/Kevs-IOS-AgentsSelf-hosted system for controlling a farm of real iPhones from a Mac with scheduling and TikTok/Instagram automation.
- minitap-ai/mobile-useAn LLM-driven agent that operates Android and iOS apps via natural language commands and returns structured data.