All postsSHORT2 min read
Expo Simulators: AI Agents Test iOS Without a Mac
Expo puts iOS simulators in the cloud for coding agents. How sessions work, what they cost, and an agent QA service idea.
Your AI agent can test your iPhone app without a Mac. Expo Simulators puts the iOS simulator in the cloud and lets your agent attach a recording to the pull request. You can watch the app run before merging.
What launched
Expo launched Expo Simulators on Nov 12, 2026: cloud iOS simulators and Android emulators built for AI coding agents. The iOS simulator can run on Expo from Linux, Windows through WSL or a cloud sandbox, with no Mac needed.
Claude Code, Codex and Cursor work with it, as does any agent that can run CLI commands. You bring the agent. Expo Simulators adds no AI model of its own.
How a session works
The agent installs your build and taps through the app. Each session runs on its own virtual machine, so parallel agents don't share a simulator.
A session keeps a full screen recording, screenshots and logs. Your agent can read the screenshots and logs, then attach the evidence to the pull request. The reviewer can watch the recording instead of pulling the branch, building it and opening a simulator.
Expo also describes a bug-triage flow: a background agent reproduces the reported bug, writes a fix, checks it on the simulator and opens a pull request with the before and after.
What it costs
Simulators is available on paid Expo plans. Starter costs $19 a month plus additional usage.
Simulator time costs $0.10 per minute for iOS and Android. Starter, Production and Enterprise include 60 minutes per month until 2027, according to the launch post. That inclusion has an end date.
The catch
The Free plan doesn't include Simulators. You'll need a build that runs on an iOS simulator or Android emulator and a project linked to Expo Services. This also supports apps outside React Native, including SwiftUI, Jetpack Compose, Flutter and Unity apps with compatible builds.
Sessions stop on their own after 2 hours at most. You can set a shorter maximum duration and an idle timeout when starting one. Sessions share your account's job concurrency and queue when capacity is full.
The builder angle (my opinion, no income guaranteed)
I'd sell app teams an agent QA service: a bug report goes in, and an agent-tested fix comes back with a recording on the pull request.
The proposed deliverable follows Expo's bug-triage example. Have the agent reproduce the issue, write the fix and check it in the simulator. Attach the recording, screenshots and logs so the team can review what happened.
Offering that workflow as a service is my suggestion. No income is guaranteed.
How to try it
Start with the Expo Simulators product page and its linked get-started docs. Use a paid Expo plan, link the project to Expo Services and prepare a simulator-compatible build.
Install the agent skill:
npx skills@latest add expo/skills --skill eas-simulator
Start an iOS simulator session:
npx eas-cli@latest simulator --platform ios
Then ask your agent to install the build, tap through the app and return the recording, screenshots and logs for the pull request.
Daily email
Get each breakdown in your inbox.
One email each evening, right after the Short goes live: the AI tool it covers, the full write-up with sources, and how to get paid for it. Free, and you can unsubscribe anytime.