eas-simulator

Run and control apps on remote iOS and Android simulators hosted on EAS cloud.

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill eas-simulator-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eas-simulator
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/eas-simulator
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill eas-simulator-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires eas-cli, agent-device, argent, and includes references (resource) components.

What problem does it solve? Developers on Linux, CI pipelines, or headless cloud agents cannot run iOS simulators locally, and macOS users sometimes need a shareable remote device. This Skill runs and drives a user's app on a remote iOS simulator or Android emulator hosted on Expo Application Services (EAS) cloud, controllable from the CLI or an AI agent. ## Core Features & Use Cases - Remote simulator sessions: Start, monitor, and stop cloud simulator sessions via the experimental eas simulator:* commands, with a live browser preview URL for iOS. - Agent-driven device control: Install apps, tap elements, fill fields, take screenshots, and record video through the agent-device or argent controllers. - Live development loop: Connect a dev build to Metro over a tunnel so code edits appear on the remote simulator via Fast Refresh. - Use Case: An AI coding agent on a Linux cloud sandbox needs to verify a UI change on iOS — it starts an EAS Simulator session, installs the dev build, connects Metro, and screenshots the result without any local Mac. ## Quick Start Ask the agent to run your Expo app on a remote cloud simulator and take a screenshot, for example: "Use EAS Simulator to run my app on a cloud iOS simulator and screenshot the home screen."

Frequently Asked Questions about eas-simulator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run my Expo app on a cloud iOS simulator?

Start a session with npx eas-cli simulator:start --platform ios, install a simulator build with agent-device install or install-from-source, then open the app and drive it via simulator:exec. Stop the session with simulator:stop when finished to end billing.

How to run an iOS simulator on Linux or in CI without a Mac?

EAS Simulator boots a remote iOS simulator on EAS cloud, which is the only option on non-macOS hosts. Set EXPO_TOKEN for headless authentication, verify access with simulator:availability, then start a session and drive it with agent-device.

Does EAS Simulator support live reload with Metro?

Yes, via Mode C: install a development build and connect the dev client to Metro over a tunnel using EXPO_UNSTABLE_TUNNEL_V2=1 expo start --tunnel. Release builds have JS baked in and can never hot-reload, so a dev build is required.

Why does my EAS Simulator screenshot show old code?

The installed build is a release or stale build whose JavaScript was bundled at build time. Rebuild with a fingerprint matching current source, or switch to a dev build connected to Metro so edits appear via Fast Refresh.

What is the difference between agent-device and argent controllers?

Both drive the remote device, but agent-device uses element refs from snapshot -i and supports launch args, while argent uses normalized 0.0-1.0 coordinates and lacks launch-args and Metro binding. agent-device is the default; argent is selected with --type argent.

When should I not use EAS Simulator?

Avoid it for local simulators on macOS (use expo run:ios or Xcode), store builds and signing (use EAS Build), web previews, and physical devices. It is a paid, limited-access EAS feature, so confirm availability before starting a session.