Expo Opens Paid-Plan Access to Cloud Simulators for AI Coding Agents

Expo announced on November 12, 2026 that Expo Simulators is available to everyone on its paid plans, giving AI coding agents cloud iOS simulators and Android emulators on which to run and verify app changes. Usage costs $0.10 per simulator minute on either platform.

The paid-plan launch expands the limited-access EAS Simulator preview Expo introduced on September 14, 2026. An Expo blog post dated November 10, 2026 was still directing developers to the waitlist, making broader paid-plan availability the new step rather than the first public demonstration of cloud devices.

Agents Get a Runtime and Reviewable Evidence

Expo’s premise is that code generation has shifted the bottleneck to verification, with agents producing changes faster than engineering teams can test and review them. Mobile adds a hardware constraint: iOS simulators run only on Apple hardware, while cloud agents typically run on Linux. An agent that cannot run the app has to assess code without seeing the resulting behavior.

The local alternative also consumes developer-machine capacity. In Expo’s example, seven agents working in parallel can require seven simulators or emulators, and Android emulators can each use 4 GB or more of RAM. Remote sessions shift that compute to Expo infrastructure and let teams run an iOS simulator from Linux, Windows through the Windows Subsystem for Linux, or a cloud sandbox without a local Mac.

The intended loop starts with a bug report in a tool such as Linear. An agent reproduces the issue, writes a fix and tests it on cloud devices in parallel, away from the developer’s machine. It can place a screen recording, screenshots and logs on the pull request, while teammates open the running build from a link without requiring a TestFlight build. The service works with Cursor, Claude Code and Codex, and adds no AI model of its own: Expo is supplying the device runtime and evidence rather than another coding model.

Expo co-founder and CTO James Ide described the intended review model: “The agent was the fast part. Expo Simulators gives every agent a simulator, so a fix arrives for review already tested on several simulators, and the only decision left is whether it’s the right code. Watch it run, then merge.”

Remote Sessions Support More Than Expo Apps

A session can be started through EAS CLI, the REST API or an authenticated creation link, according to the Expo Simulators documentation. The session can install an Expo Build, a build whose native code matches the project’s fingerprint, an application archive or Expo Go; without an application source, it starts with a blank device. Agents and test jobs can control apps through agent-device, Argent or Appium, while a browser preview lets people watch the run. The official Expo Simulators skill packages access checks, build preparation, session limits, device control, evidence collection and cleanup for agents.

The product page lists support for React Native, Swift, Kotlin, Flutter, Unity and other frameworks. Apps do not have to be built with Expo or React Native, but the build must run on an iOS Simulator or Android Emulator and the project must be linked to Expo Services. Each session runs in an isolated environment with session-scoped credentials and access-controlled previews, and stopping it disables the simulator and controller endpoints.

Paid Access Comes With Usage and Capacity Limits

On Expo’s pricing page, the Starter, Production and Enterprise plans each include 60 simulator minutes per month until 2027, with usage-based pricing beyond that allowance. Paid sessions can run for up to 115 minutes.

Parallelism does not create unlimited account capacity. The usage and billing guide says simulator sessions draw on the account’s job concurrency and queue when no capacity is free. Ending a CI job or returning from a non-interactive command also does not stop the remote device. Teams must stop it explicitly or rely on a duration or idle limit; otherwise, an unattended session continues consuming usage. That makes cleanup and session limits part of cost control for automated workflows.

The limitations guide adds three material qualifications: the simulator CLI commands remain experimental, the service does not provide physical devices, and recordings may miss frames and therefore cannot prove or disprove a brief frame drop. A cloud runtime can verify app behavior, but it does not eliminate the need for physical-device testing or profiling where those tools are required.

Expo’s next disclosed step is Agent Sessions, a planned enterprise layer for triggering agents from sources such as customer feedback and protecting against prompt injection, where malicious input could direct an agent to expose data. Expo expects to share details by the end of November 2026; this is a roadmap item rather than a capability included in the current launch.

Simulators adds a verification stage to Expo’s existing build, CI/CD, app-store submission, over-the-air update and monitoring services. The result is a division of labor rather than an autonomous release process: agents supply tested changes and runtime evidence, account limits govern how much runs at once, and people retain the merge decision.