eas-simulator
An agent skill by expo, from expo/skills. Tags: android, debugging, ios, mobile, sandbox, testing.
What it does
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to run/install/screenshot my app', 'I'm on Linux/Cursor and need an iOS device', 'no sim on this box / headless CI', 'let an agent click through my app and screenshot it', 'test my dev build on a remote sim with live reload', 'stream a sim to my browser' - even when they don't say 'EAS Simulator' or 'cloud'. On a host WITHOUT a local simulator (Linux, CI, cloud sandbox) it's the default; on macOS, do NOT auto-trigger for a plain 'run on the simulator' - use it only for a cloud/remote/shareable sim, an iOS version they lack, or an agent-driven session. NOT for local sims (expo run:ios, Xcode, Android Studio), EAS Build/Update, web preview, or physical devices.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill eas-simulator
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/expo/skills
cp -r skills/plugins/expo/skills/eas-simulator ~/.claude/skills/eas-simulator
Safety box score
Grade F, high risk: 77 of 100 risk points, rated 2026-10-17. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill launches and drives remote Expo/EAS simulator sessions, installs app builds, tunnels Metro/dev-server traffic through Expo infrastructure, and can fetch logs, crashes, and recordings. The main risks are broad network exposure, session and API tokens stored in local config files, and execution of current upstream CLI packages at runtime.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 3 (high) | It runs network-fetched tooling directly via `npx --yes eas-cli@latest`, `npx agent-device@latest`, and even `npm install -g @swmansion/argent`, so installing the skill authorizes execution of downloaded code. |
| Network access | 3 (high) | Its purpose is to create cloud sessions, browser previews, and tunnels such as `EXPO_UNSTABLE_TUNNEL_V2=1 expo start --tunnel`, which exposes local Metro/dev-server traffic to Expo/EAS infrastructure and remote browsers. |
| Filesystem reach | 2 (moderate) | It writes and resets `.env.eas-simulator`, may ask to edit `.gitignore`, and can create config files like `.cursor/mcp.json` / `.claude/mcp.json` or `~/.argent/` entries. |
| Secrets & credentials | 3 (high) | The skill stores session IDs and daemon tokens in `.env.eas-simulator`, uses `EXPO_TOKEN` / `ARGENT_AUTH_TOKEN`, and says `remoteConfig.previewApiUrl` already contains a session token in its query. |
| Privilege & persistence | 2 (moderate) | It includes user-wide changes like `npm install -g @swmansion/argent` and editor/CLI config writes, but it does not require sudo or system service setup. |
| Instruction hijack surface | 1 (low) | It pushes non-interactive execution (`--yes`, `--non-interactive`) and says to 'start the session and do the requested work without asking again,' which reduces confirmation points but is not hostile prompt injection. |
| Irreversible actions | 2 (moderate) | It can start billable cloud sessions, install builds, drive the simulator, keep sessions alive, and stop them, so it has meaningful side effects on Expo infrastructure and account usage. |
| Transparency | 3 (high) | A lot of the actual executed code is fetched at runtime from `@latest` packages and experimental hidden CLI commands, so the reviewer cannot fully inspect what will run from the repo alone. |
Before installing
- Read `SKILL.md` and `references/run-your-app.md` first; they use `npx --yes ...@latest` and will fetch code from npm at runtime.
- Make sure `.env.eas-simulator` and any MCP config files are gitignored before you start.
- Use a throwaway Expo account or test project first if you want to understand the session tokens and billing behavior.
- Confirm you actually want a public tunnel from your local Metro port to Expo/EAS cloud for the session.
Rated 2026-10-17 by an automated review of 6 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/eas-simulator/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- eas-app-stores — EAS service (paid). Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play.
- expo-brownfield — Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app.
- expo-app-clip — Framework (OSS). Add an iOS App Clip target to an Expo app.
- expo-dev-client — Framework (OSS). Build and distribute Expo development clients locally or via TestFlight for internal testing.
- expo-native-ui — Framework (OSS). Build beautiful, native-feeling Expo screens.
- expo-ui — Framework (OSS). Build native UI with the @expo/ui package: real SwiftUI on iOS and Jetpack Compose on Android.