eas-simulator

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

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/sombek/fitness-guidance-app --skill eas-simulator-sombek
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eas-simulator
Source: https://github.com/sombek/fitness-guidance-app/tree/main/mobile/.agents/skills/eas-simulator
Command: npx skills add https://github.com/sombek/fitness-guidance-app --skill eas-simulator-sombek

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 an iOS simulator locally, and macOS users sometimes need a shareable remote device. This Skill runs your Expo app on a remote iOS simulator or Android emulator hosted on EAS cloud, so an agent can install, drive, screenshot, and record the app without any local simulator. ## Core Features & Use Cases - Remote simulator sessions: Start, monitor, and stop cloud simulator sessions via the experimental eas simulator:* CLI commands, with a live browser preview URL on iOS. - Agent-driven device control: Drive the remote device with agent-device (or argent) verbs — open apps, tap elements, fill fields, take screenshots, and record video of animations. - Three run modes: Install a local Release build, install an EAS build artifact, or connect a dev build to Metro over a tunnel for live Fast Refresh edits. - Use Case: You are on a Linux CI box and need to verify a checkout flow on iOS. The Skill checks availability, starts a named session, installs your dev build, connects Metro, taps through the flow, and returns screenshots — then stops the session to end billing. ## Quick Start Ask the agent to run your app on a cloud iOS simulator and take a screenshot of the main 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?▼

EAS Simulator is the supported path since Linux cannot run local iOS simulators. Set EXPO_TOKEN for headless authentication, verify access with simulator:availability, then start a remote session and drive it with agent-device commands.

Does EAS Simulator support live reload with Metro?▼

Yes, via Mode C: install a development build (developmentClient: true) and connect it to Metro over a tunnel using EXPO_UNSTABLE_TUNNEL_V2=1 expo start --tunnel. Release builds have baked-in JavaScript and can never hot-reload.

Why does my eas simulator:start command fail?▼

Common causes are an outdated eas-cli (simulator commands need version 20.3.0 or later, run via npx eas-cli@latest), missing authentication, or the account not being enabled for this limited-access feature. Check access first with simulator:availability --json.

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

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

When should I not use EAS Simulator?▼

Avoid it for local simulators on macOS (use expo run:ios or Xcode), for store builds and signing (use EAS Build), for web previews, and for physical devices. It is a paid EAS service, so local options are preferred when available.