Running mobile simulators

A virtual mobile device exists outside the workspace that uses it. Bind each agent session to one workspace, one exact device, and the processes that the agent starts. Agents that share a worktree still need separate devices and leases.

Establish the session boundary

Before a device state change, resolve the workspace's real path and inventory:

• connected Android emulator serials and iOS simulator UDIDs;
• active emulator, Simulator, Maestro, MCP, and Viewer processes; and
• active leases or other repository-specific device coordination.

Read Device leases before selecting or starting a device. On a host that can run more than one workspace, an exclusive device lease is mandatory. Inventory is read-only; do not launch a device, install or start an app, run automation, or change device state until the lease is held.