eas-simulator

Name: eas-simulator
Author: expo

3.2kinstalls117forks

How to install eas-simulator?

expo/skills/eas-simulator

$npx -y skills add expo/skills --skill eas-simulator

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# EAS Simulator
2
3	> EAS service - costs apply. EAS Simulator runs on Expo Application Services cloud infrastructure, a paid product with free-tier limits; remote simulator sessions use your plan's compute allowance. See https://expo.dev/pricing.
4
5	EAS Simulator runs a remote iOS simulator or Android emulator on EAS infrastructure that you drive from your machine — from the CLI, from an AI agent (via `agent-device`), and from a browser preview. It's the unlock for environments that can't run a simulator locally (Linux boxes, cloud/background agents like Cursor Cloud), and for letting an agent verify a change on a real device instead of only reasoning about code.
6
7	The `simulator:` commands are experimental and hidden, and need a recent eas-cli (≥ 20.3.0 as of writing) — which is why this skill runs everything via `npx --yes eas-cli@latest`. Flags and verbs may change; if a command fails, `<cmd> --help` is authoritative.*
8
9	## When to use
10
11	The frontmatter `description` carries the trigger phrases. In short: use this to get a user's app onto a cloud simulator and interact with it — especially from a Mac-less or cloud/sandbox agent. Not for local sims (`expo run:ios`, Xcode, Android Studio), store builds/signing (that's EAS Build), or physical devices. For the macOS case, see Cloud vs local next.
12
13	## Cloud vs local: decide this first
14
15	- Non-macOS (Linux / CI / cloud sandbox like Cursor Cloud, detect via `uname -s` ≠ `Darwin`): the only way to get a sim — just proceed.
16	- macOS: local sims exist and a cloud session costs money + latency, so ask first ("a remote cloud sim — to share a live preview, offload, or test an iOS version you lack — or just run locally?") unless the user explicitly said cloud/remote/shareable.
17	- Always honor an explicit choice; for "run it locally" hand off to `expo run:ios` / Xcode.
18
19	```bash
20	# Programmatic detection — run this to decide before doing anything else:
21	if [ "$(uname -s)" != "Darwin" ] \|\| ! xcrun --find simctl &>/dev/null 2>&1; then
22	echo "no local sim — proceed with EAS Simulator"
23	else
24	echo "local sim available — ask the user (cloud or local?)"
25	fi
26	```
27
28	## Prerequisites
29
30	- Run every `eas` command via `npx --yes eas-cli@latest …` — guarantees a CLI new enough to have `simulator:*` (a global `eas` is often too old), and `--yes` skips npx's prompt. (Bare `eas` is fine if `eas --version` is current.)
31	- Authenticated. Interactive machine → `npx --yes eas-cli@latest login`. Cloud sandbox / CI / headless agent has no browser login — set `EXPO_TOKEN` (expo.dev → Account → Access Tokens) in the env instead. Verify either way with `npx --yes eas-cli@latest whoami`.
32	- Run from an Expo project directory. A fresh app needs one-time setup: `npx --yes eas-cli@latest init` to create/link the project (when there's no `projectId`), and set `ios.bundleIdentifier` in app config if it's missing — a fresh `create-expo-app` often has none, and `prebuild`/`eas build` need it (they prompt or fail without it; e.g. `dev.<owner>.<slug>`). Read current config with `npx expo config --json` (it may live in `app.config.js`). The first Mode-C run is slow (native build); later runs reuse it.
33	- A controller to drive the device. This skill uses agent-device (open source, MIT), run on demand via `npx agent-device@latest` — nothing globally installed. argent is an alternative (`--type argent` in `simulator:start`); see [references/controllers.md](./references/controllers.md).
34	- `.env.eas-simulator` is written/managed by eas-cli (not this skill): it holds the session id (`EAS_SIMULATOR_SESSION_ID`) + the daemon URL/token, so `get`/`stop`/`exec` default to that session (usually omit `--id`; pass `--id <id>` to target another). It car

People who liked this also viewed

6 picks

Type

eas-simulator

3.2kinstalls117forks

View on GitHub

How to install eas-simulator?

expo/skills/eas-simulator

$npx -y skills add expo/skills --skill eas-simulator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# EAS Simulator
2
3	> EAS service - costs apply. EAS Simulator runs on Expo Application Services cloud infrastructure, a paid product with free-tier limits; remote simulator sessions use your plan's compute allowance. See https://expo.dev/pricing.
4
5	EAS Simulator runs a remote iOS simulator or Android emulator on EAS infrastructure that you drive from your machine — from the CLI, from an AI agent (via `agent-device`), and from a browser preview. It's the unlock for environments that can't run a simulator locally (Linux boxes, cloud/background agents like Cursor Cloud), and for letting an agent verify a change on a real device instead of only reasoning about code.
6
7	The `simulator:` commands are experimental and hidden, and need a recent eas-cli (≥ 20.3.0 as of writing) — which is why this skill runs everything via `npx --yes eas-cli@latest`. Flags and verbs may change; if a command fails, `<cmd> --help` is authoritative.*
8
9	## When to use
10
11	The frontmatter `description` carries the trigger phrases. In short: use this to get a user's app onto a cloud simulator and interact with it — especially from a Mac-less or cloud/sandbox agent. Not for local sims (`expo run:ios`, Xcode, Android Studio), store builds/signing (that's EAS Build), or physical devices. For the macOS case, see Cloud vs local next.
12
13	## Cloud vs local: decide this first
14
15	- Non-macOS (Linux / CI / cloud sandbox like Cursor Cloud, detect via `uname -s` ≠ `Darwin`): the only way to get a sim — just proceed.
16	- macOS: local sims exist and a cloud session costs money + latency, so ask first ("a remote cloud sim — to share a live preview, offload, or test an iOS version you lack — or just run locally?") unless the user explicitly said cloud/remote/shareable.
17	- Always honor an explicit choice; for "run it locally" hand off to `expo run:ios` / Xcode.
18
19	```bash
20	# Programmatic detection — run this to decide before doing anything else:
21	if [ "$(uname -s)" != "Darwin" ] \|\| ! xcrun --find simctl &>/dev/null 2>&1; then
22	echo "no local sim — proceed with EAS Simulator"
23	else
24	echo "local sim available — ask the user (cloud or local?)"
25	fi
26	```
27
28	## Prerequisites
29
30	- Run every `eas` command via `npx --yes eas-cli@latest …` — guarantees a CLI new enough to have `simulator:*` (a global `eas` is often too old), and `--yes` skips npx's prompt. (Bare `eas` is fine if `eas --version` is current.)
31	- Authenticated. Interactive machine → `npx --yes eas-cli@latest login`. Cloud sandbox / CI / headless agent has no browser login — set `EXPO_TOKEN` (expo.dev → Account → Access Tokens) in the env instead. Verify either way with `npx --yes eas-cli@latest whoami`.
32	- Run from an Expo project directory. A fresh app needs one-time setup: `npx --yes eas-cli@latest init` to create/link the project (when there's no `projectId`), and set `ios.bundleIdentifier` in app config if it's missing — a fresh `create-expo-app` often has none, and `prebuild`/`eas build` need it (they prompt or fail without it; e.g. `dev.<owner>.<slug>`). Read current config with `npx expo config --json` (it may live in `app.config.js`). The first Mode-C run is slow (native build); later runs reuse it.
33	- A controller to drive the device. This skill uses agent-device (open source, MIT), run on demand via `npx agent-device@latest` — nothing globally installed. argent is an alternative (`--type argent` in `simulator:start`); see [references/controllers.md](./references/controllers.md).
34	- `.env.eas-simulator` is written/managed by eas-cli (not this skill): it holds the session id (`EAS_SIMULATOR_SESSION_ID`) + the daemon URL/token, so `get`/`stop`/`exec` default to that session (usually omit `--id`; pass `--id <id>` to target another). It car

People who liked this also viewed

6 picks

Type