Put an agent on your phone: two routes, one red line
A hands-on SOP for putting a phone AI agent onto real hardware, offering two routes side by side. The first section decides whether it is worth doing at all: it fits a spare handset used to test whether a phone can genuinely run errands, and it does not fit a daily driver, an unattended long task, or anything involving payment, password changes, sending messages or account settings. Route A is OmniBot's on-device app form: install the APK from Releases, then configure AI capability, provider and scene models in settings, where Memory embedding strictly needs an embedding model and other scenes are best served by multimodal or vision models; the Alpine environment initializes on startup; sending a skills repository link to the assistant installs skills; scheduled tasks run subagent flows while alarms only remind; an optional Remote Codex bridge lets the phone scan a code to borrow a computer's Codex; and an optional WebUI takes an address and token from the in-app local service, defaulting to port 8899 with no trailing path. Development requires Flutter 3.47.2+, JDK 17+, Node.js 20.19+ or 22.12+ and pnpm 10.28.0. Route B is OpenGUI's framework form reached through DeepSeek Harness: the hard prerequisites are an Android 11 (API 30) or newer device or emulator plus USB debugging and accessibility permission; the shortest path is pasting the official install prompt to Codex, after which the installer verifies SHA-256, installs only the OpenGUI plugin and preserves unrelated plugins and settings; version discipline supports DSH 0.1.0-rc.7, 0.1.0-rc.8, 0.1.1-rc.1 and 0.1.1-rc.2 with new installs defaulting to 0.1.1-rc.2, does not support 0.1.2-alpha.4, and refuses a downgrade from a 0.1.1 RC to a 0.1.0 RC. Once a real device is connected, a single prompt verifies the setup. The safety section covers a spare device, least privilege, a hard rule of per-action human confirmation, trusted LAN only, tokens that never leave the machine, retained logs for audit, and short tasks before long ones, backed by a pre-flight checklist and a seven-row pitfall table. Licence boundaries get their own section: OmniBot requires a commercial licence for commercial use since AGPL v3 covers only non-commercial and personal, educational or research use, while OpenGUI is BSL 1.1 for non-production use only. The article also notes it does not overlap with the site's desktop computer-use build SOP, and invents no pricing or limits absent from the official docs, writing instead that the vendor governs.