Command Palette

Search for a command to run...

UnylyUnyly
Назад к скиллам

eas-simulator

БесплатноБез исполняемых скриптовНе проверен

Run and control a user's app on a remote iOS/Android simulator with Expo Simulators (also called EAS Simulator). Read before running any `eas simulator:*` comma

Об этом скилле

Expo Simulators

EAS service - costs apply. Sessions count toward your account's pricing and limits and stop at their maximum duration. Stop a session with eas simulator:stop when the task is done. See https://expo.dev/pricing for current terms.

Expo Simulators 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.

Naming. The service is called Expo Simulators. "EAS Simulator" is an internal name that is still in use, and the CLI commands are eas simulator:* (alias eas sim:*). All of these names mean the same service: treat a request that uses any of them as a request for this skill. When you talk to the user about the service, call it Expo Simulators. Keep the exact command names (eas simulator:start) in commands.

The simulator:* commands need a recent eas-cli, and new flags arrive often — which is why this skill runs everything via npx --yes eas-cli@latest. The relevant subcommand's --help output is authoritative.

When to use

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.

Cloud vs local: decide this first

  • Explicit cloud/remote/shareable request: use Expo Simulators after checking access, on any host.
  • Generic simulator request: use a suitable local simulator when available. If the host cannot run the requested simulator (for example, iOS on Linux or a cloud sandbox), use Expo Simulators after checking access. A non-macOS host may still support a local Android emulator.
  • Honor an explicit local choice; hand off to expo run:ios / Xcode / Android Studio as appropriate. Clarify only when the requested environment remains ambiguous and affects the task.

When the user asks for Expo Simulators, EAS Simulator, or a cloud simulator, start the session and do the requested work without asking again. Stop the session when the work is done. Only check in if the user set a limit you would go past, or if the work grows beyond what they asked for.

Prerequisites

  • 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.)
  • 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.
  • 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.
  • 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. Appium and argent are alternative automation interfaces; web-preview-only has no automation interface. See references/controllers.md.
  • .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 carries a token → keep it gitignored (eas-cli marks it "do not commit" but may not add the ignore rule, and a fresh app's .gitignore won't cover it — add .env.eas-simulator if missing).
  • The command blocks assume a POSIX shell (bash/zsh) — printf, lsof, $(seq …) loops won't run in cmd/PowerShell. On Windows, run them in WSL or Git Bash, or translate as you go (the eas-cli/agent-device invocations themselves are cross-platform).

Session lifetime

  • --max-duration-minutes N is the hard automatic-stop deadline. You can set it up to the plan limit (115 minutes on paid plans). The timer starts when the session is ready.
  • --max-idle-time-minutes N stops a session after that many inactive minutes. Omitted means no idle timeout: the session runs until its maximum duration or an explicit stop.
  • Controller activity resets the idle timer (agent-device, argent, and Appium commands, which are recorded as session events with producer appium). On iOS, browser input and some simulator:control actions (such as app launches and screenshots) also reset it. Watching the preview does not reset it, and neither does browser input on Android. For a user-driven browser preview, rely on the maximum duration, not idle time, to bound the session. Android web-preview-only sessions reject --max-idle-time-minutes.

Check availability first

Expo Simulators is available on paid EAS plans only. The Free plan has no access. Check access before starting a session; this read-only command does not create a session.

npx --yes eas-cli@latest simulator:availability --json
# → {"available": true, "accountName": "..."}  enabled → continue to the core loop
# → {"available": false, "accountName": "..."} not enabled → do NOT start a session

If it's not available, don't call simulator:start (it will fail). Instead, hand off gracefully so you keep making progress without this skill:

  • Tell the user Expo Simulators needs a paid EAS plan, and point them to their account's billing page to upgrade: https://expo.dev/accounts/<accountName>/settings/billing (use accountName from the output). Plans are compared at https://expo.dev/pricing. Give only these links, even if the output has other links.
  • Fall back to their normal local path for the actual goal — expo run:ios / Xcode / Android Studio for a local sim/emulator, an EAS Build, or whatever else fits. Don't dead-end on the cloud sim; the request was almost never "use Expo Simulators specifically."

(If simulator:availability isn't recognized, the CLI is too old — upgrade, or treat a not enabled for this account error from simulator:start the same way: stop and fall back.)

Choose a device before starting

Use the server's current device catalog instead of guessing names or copying a static list:

npx --yes eas-cli@latest simulator:devices                         # both platforms
npx --yes eas-cli@latest simulator:devices --platform ios          # iPhones and iPads
npx --yes eas-cli@latest simulator:devices --platform android      # phones and tablets
npx --yes eas-cli@latest simulator:devices --json                  # identifiers and display names by platform

This read-only command requires an Expo login or EXPO_TOKEN, but no running session or linked project. Copy the exact identifier (the table's --device value) into simulator:start --platform <ios|android> --device <identifier>. Quote names containing spaces or parentheses. For example, use --device "iPad mini (A17 Pro)" on iOS or --device pixel_tablet on Android when listed.

Omit --device to let the server choose its current default. Do not hardcode a default or infer it from

Установить eas-simulator в Claude Code и Claude Desktop

Зарегайся, чтобы установить скилл

Создай бесплатный аккаунт, чтобы открыть команду установки и сохранить скилл в библиотеку.

  • Открой команду установки в одну строку
  • Сохраняй скиллы в синхронизируемую библиотеку
  • Уведомления, когда скиллы обновляются
Зарегаться бесплатноУ меня уже есть аккаунт

Разрешённые инструменты

Инструменты, которые скиллу разрешено вызывать.

Bash(npx *eas-cli@*)
Bash(npx *agent-device@*)
Bash(npx expo *)
Bash(eas *)
Bash(expo *)
Bash(xcodebuild*)
Bash(pod*)
Bash(argent *)
Bash(ffmpeg*)

Вложенные файлы

agents/openai.yamlreferences/controllers.mdreferences/logs-and-crashes.mdreferences/run-your-app.mdreferences/troubleshooting.md

FAQ

Что делает скилл eas-simulator?

Run and control a user's app on a remote iOS/Android simulator with Expo Simulators (also called EAS Simulator). Read before running any `eas simulator:*` commands - it has the current syntax and workflow. 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 'Expo Simulators', '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.

Как установить скилл eas-simulator?

Скопируй папку скилла в ~/.claude/skills (вкладка Claude Code выше делает это одной командой), либо поставь как плагин.

Скилл eas-simulator запускает скрипты?

Нет, скилл состоит только из инструкций (SKILL.md), без исполняемых скриптов.

Похожие скиллы

Сравнить eas-simulator с