A phone is a different workspace.
Choose the environment your task needs.
| Task | Phone sandbox | Computer sandbox |
|---|---|---|
| Interface | Mobile apps, touch and phone screens | Desktop apps, browser and terminal |
| Control | Screen text, UI elements, tap, type and swipe | Shell commands, files, browser and desktop controls |
| Good fit | Mobile app workflows and app testing | Building code, running services and desktop work |
Why give an agent a phone?
An API integration exposes selected features. A phone gives the agent the app’s interface, including workflows without a matching integration.
It also means dealing with that app’s login, permissions and interface. A phone does not guarantee that every app works or every task succeeds.
What stays with the phone?
Apps, files and runtime state live inside its own encrypted VM. Forking copies a phone’s state into another phone.
Phones are ephemeral. A host reboot can end them; they are not a durable backup. Named snapshots and reboot persistence are in development.
Is it faster?
It depends on the task and tools. Provisioning time, screen latency and total task time measure different things. We do not claim that phone use is faster for every task.