[01] Run anywhere
Same commands. Any device, anywhere.
Your agent keeps the same agent-device workflow when it leaves your laptop: replay in CI, run from Linux against a Mac that hosts the simulators, or drive hosted devices in a device cloud.
- Local
On your machine
Simulators, emulators and physical devices on your Mac or Linux box. Sessions follow your git worktree, so parallel agents don’t take over each other’s devices.
$ agent-device open MyApp --platform iosRead the guide: On your machine - CI
On every pull request
Replay saved
.adscripts withagent-device test, keep screenshots and logs as artifacts, and report to JUnit.$ agent-device test ./workflowsRead the guide: On every pull request - Remote
On a device host
Run the agent on Linux or in a cloud workspace and execute on the Mac or Linux host that has the devices, through the remote proxy.
$ agent-device proxy --port 4310Read the guide: On a device host - Device clouds
On hosted devices
The same commands drive BrowserStack, AWS Device Farm and Limrun devices built in, TestMu AI through its provider plugin, and Expo Simulators on EAS.
$ agent-device connect limrun --platform iosRead the guide: On hosted devices
[02] Device clouds
Hosted devices, same session model.
Connect a provider and your agent opens, reads and drives its devices with the commands it already uses. Which evidence each provider returns differs; compare them before you pick.
[03] For teams
Need devices for your team? Talk to Callstack.
We help teams connect agent-device to their CI and pull request reviews, set up shared iOS and Android device hosts, and run agent-driven QA.