PokeClaw puts Gemma 4 in charge

This is a strong proof point for local agent UX on mobile: the moment an LLM can inspect UI state and drive real apps offline, “phone assistant” stops being a demo trope and starts looking like a product category.

• –The main technical hook is the closed loop on-device stack: screen understanding, tool selection, action execution, and re-reading the result all happen locally.
• –The repo frames it as CPU-capable, but the practical ceiling is still hardware-bound; the README says a budget phone can take around 45 seconds to warm Gemma 4 E2B.
• –Accessibility-based control is more robust than coordinate tapping, but it still inherits every UI edge case, permission prompt, and app-specific inconsistency that makes mobile automation brittle.
• –If this works as advertised, the bigger story is privacy by architecture rather than policy: there is no server to subpoena, log, or monetize.
• –The open-source angle matters too; even if the first release is rough, it gives developers a concrete starting point for local mobile agents instead of another cloud-first assistant.