Simulators built for agents

Yes. Any coding agent that can run shell commands can start a session, install a build, and interact with your app. Claude Code, Codex, and Cursor all work. Install the eas-simulator skill to help your agent handle setup, device control, and evidence collection.

No. Expo Simulators works with apps built using React Native, Swift, Kotlin, Flutter, Unity, and other frameworks. All you need is a build that runs on an iOS Simulator or Android Emulator and a project linked to Expo Services.

Yes. Start sessions from GitHub Actions, Expo Workflows, or another CI system through the EAS CLI or REST API. Your CI runner can install a build, run checks, and collect results.

Yes. Connect your Appium test suites to an Appium server provisioned for your session. You can also run supported Maestro YAML flows through agent-device. Expo Simulators supports a subset of Maestro commands.

Yes. Run multiple sessions to test different changes, devices, or flows in parallel. Sessions share your account’s job concurrency and queue when capacity is full. See your plan’s concurrency limits on our pricing page.

Expo Simulators supports iPhone and iPad simulators and Android emulators. Choose a device when you start a session. Available iOS versions depend on the session image; Android sessions support selecting a compatible system image. See the current device catalog in the Expo Simulators docs for available options.

Yes. Share a live simulator session so your team can review the running app without setting up a development environment. You can also add a link to a pull request that starts a new session with that build. Preview links require an Expo login with project access by default; starting a new session requires the Developer role or higher.

Yes. Expo Simulators records the session and stores captured screenshots and job logs. Your agent or CI workflow can post links to that evidence on a pull request, so your team can review what happened during testing.

Yes. Each session runs in an isolated environment on Expo infrastructure. Your Expo account role controls who can start, view, or stop sessions, and preview links require an Expo login with project access by default. When a session stops, its simulator and controller endpoints are no longer available.

No. For Expo and React Native apps, Expo Workflows can use fingerprinting to find an existing build with matching native code, then repack it with your latest JavaScript, skipping a full native rebuild. During development, connect a development build to Metro to see edits through Fast Refresh.