
Serve Simulator
FreeControl and stream Apple Simulators with ease.
Free · Opens the source repo
What Serve Simulator does
Serve Simulator is a powerful tool that allows developers to interact with and control Apple Simulators for iOS, iPad, and Apple Watch. By utilizing the serve-sim CLI, users can perform a wide range of actions including sending taps, swipes, and hardware button presses to the simulator, as well as streaming the simulator's display to a web browser. This skill effectively bridges the gap between development and testing, enabling seamless interaction with the simulator environment.
The skill operates by spawning a Swift helper that captures the simulator's framebuffer and exposes it as an MJPEG stream. This allows developers to preview their applications in real-time while also providing a binary WebSocket input channel for sending gestures and commands. The included reference materials guide users through the various commands and workflows, ensuring that they can leverage the full capabilities of the simulator effectively.
Ideal for developers working on iOS applications, Serve Simulator facilitates tasks such as injecting synthetic camera feeds, toggling CoreAnimation debug overlays, and managing app permissions. By providing a comprehensive set of commands, it allows for detailed testing and debugging of applications in a simulated environment, making it an essential tool for any iOS developer looking to streamline their workflow.
However, it's important to note that Serve Simulator is specifically designed for use with Apple Simulators on macOS, and is not suitable for Android emulators or real iOS devices. This specialization means that while it excels in its intended use case, it may not be the right choice for developers working outside the Apple ecosystem.
When to use it
Use this skill when you need to control an Apple Simulator for testing or debugging purposes, especially when streaming the simulator output is required.
When not to use it
Avoid this skill if you are working with Android emulators or need to build/install apps directly on iOS devices.
What you can build with it
Automated UI Testing
Leverage Serve Simulator to automate UI interactions and validate application behavior in the simulator.
Remote App Review
Stream the simulator output to a web browser for remote review and collaboration with team members.
Debugging Core Animation Issues
Use the CoreAnimation debug features to analyze and optimize animations in your iOS applications.
How to install Serve Simulator
View source1. Install with the skills CLI
npx skills add evanbacon/serve-sim/serve-sim --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by evanbaconserve-sim
Drive an Apple Simulator (iOS, iPad, Apple Watch) from an agent using the serve-sim CLI. serve-sim spawns a Swift helper that captures the simulator framebuffer via simctl io, exposes it as an MJPEG stream plus a binary WebSocket input channel, and serves a React preview UI on top. This skill teaches an agent the exact CLI surface, the gesture JSON shape, the gotchas, and the recommended workflows.
When to use
- The user wants an agent to tap, swipe, drag, pinch, or send hardware buttons to a running Apple Simulator.
- The user wants to stream a simulator to a browser (local, LAN, or tunneled) for review or remote control.
- The user wants to inject a synthetic camera feed (file, webcam, or animated placeholder) into a specific app on the simulator.
- The user wants to toggle CoreAnimation debug overlays (off-screen rendering, blended layers, slow animations) for performance work.
- The user wants to simulate a memory warning or rotate the device programmatically.
- The user wants to read the simulator's accessibility tree to find UI elements without pixel hunting.
- The user wants to grant, revoke, or reset an app's privacy permissions — camera, photos, location, contacts, or push notifications.
When NOT to use
- Android emulators → use
adb shelltooling. - Building or installing an iOS app → use
xcodebuildorxcrun simctl install. - React Native in-app runtime debugging (Redux state, network inspection, component tree) → use rn-debugger tooling.
- Real iOS hardware devices → use
xcrun devicectlor Xcode.
Prerequisites
Before any other action, verify the host satisfies these. If something is missing, tell the user exactly what to install — do not proceed.
| Requirement | Check command | Why |
|---|---|---|
| macOS host | uname -s returns Darwin | serve-sim only runs on macOS |
| Xcode CLI tools | xcrun --version exits 0 | simctl is the underlying simulator driver |
| Node.js ≥18 | node --version ≥18 | serve-sim is an npm package run via npx |
| macOS 14+ (optional) | sw_vers -productVersion ≥14 | Required ONLY for camera subcommand |
A bundled helper script is available: scripts/check-prereqs.sh. Run it; if it exits non-zero, surface the message to the user.
A booted simulator is required for most subcommands. Check with xcrun simctl list devices booted. If none are booted, tell the user to open Xcode → Simulator or to run xcrun simctl boot <UDID>.
Mental model
┌──────────────┐ simctl io ┌─────────────────┐ MJPEG / WS ┌─────────┐
│ iOS Simulator│ ──────────► │ serve-sim-bin │ ───────────► │ Browser │
└──────────────┘ (Swift) │ (per-device) │ └─────────┘
└─────────────────┘
▲
state file in
$TMPDIR/serve-sim/
▲
┌──────────────────┐
│ serve-sim CLI │
└──────────────────┘
Key invariants the agent must respect:
- All coordinates are normalized 0..1, with
(0, 0)at top-left and(1, 1)at bottom-right of the display. Never pass pixel coordinates. - One helper per device. Multiple booted simulators are supported by passing several device names or by attaching to all.
- State lives in
$TMPDIR/serve-sim/server-{udid}.json. Useserve-sim --listto query it; do not read the JSON directly unless you know what you are doing. - The orientation set via
rotateis remembered by the helper, and subsequent gestures are rotated client-side. An agent that sends raw coords after a rotation does not need to compensate manually.
Common operations
| Goal | Command | Notes |
|---|---|---|
| Start preview server | npx serve-sim [device] | Default preview at http://localhost:3200, stream at :3100. Foreground process. |
| Start headless / daemon | npx serve-sim --detach [device] | Returns JSON with pid, port, url. Use for agent loops. |
| Show stream in host's preview | npx serve-sim --detach -q → hand off url to host preview tool | See "Showing the stream in your agent's preview" section. |
| List running streams | npx serve-sim --list | Add -q for JSON-only output. |
| Stop all helpers | npx serve-sim --kill | Pass [device] to stop a specific one. |
| Single tap | npx serve-sim tap <x> <y> | <x> <y> in 0..1. Use this, not gesture, for plain taps. See "Critical gotcha" below. |
| Multi-step gesture | npx serve-sim gesture '<json>' | See references/gestures.md. |
| Hardware button | npx serve-sim button <name> | Names: home, swipe_home, app_switcher, lock, siri, side_button. See references/buttons-rotation.md. |
| Rotate device | npx serve-sim rotate <orientation> | portrait, portrait_upside_down, landscape_left, landscape_right. |
| Simulate memory warning | npx serve-sim memory-warning | Equivalent to Debug → Simulate Memory Warning. |
| CoreAnimation debug | npx serve-sim ca-debug <option> <on|off> | Options: blended, copies, misaligned, offscreen, slow-animations. See references/ca-debug.md. |
| Inject camera feed | npx serve-sim camera <bundle-id> [--file <path>|--webcam [name]] | (Re)launches the app with the camera dylib attached. macOS 14+ only. See references/camera.md. |
| Hot-swap camera source | npx serve-sim camera switch <placeholder|webcam|file> [arg] | No app relaunch. |
| Manage app permissions | npx serve-sim permissions <grant|revoke|reset|list> <permission> <bundle-id> | Camera, photos, location, push notifications, contacts, etc. See references/permissions.md. |
| Read accessibility tree | curl http://localhost:3100/ax | Returns axe-style JSON. See references/endpoints.md for all endpoints. |
Most subcommands accept -d <udid|name> to target a specific device when several are booted.
Critical gotcha: prefer tap over gesture for taps
Each serve-sim gesture call opens its own WebSocket. If you issue two back-to-back gesture calls — one with {"type":"begin",...} and one with {"type":"end",...} — the simulator receives them with enough latency between them that the touch is interpreted as a long-press, not a tap. This is a deliberate constraint of the protocol, not a bug to work around.
Rule: for any single-shot tap, use serve-sim tap <x> <y>. Only use gesture for drags, swipes, or multi-step interactions where you must thread the same socket across begin → move × N → end.
Targeting a specific device
When multiple simulators are booted, every subcommand accepts -d <udid|name>. The name match is case-insensitive against the device name returned by xcrun simctl list devices booted. Examples:
npx serve-sim tap 0.5 0.5 -d "iPhone 16 Pro"
npx serve-sim button home -d ABC12345-...
npx serve-sim --list # show all running streams
If the user has only one booted simulator, omit -d entirely. The skill should prefer auto-detection over hard-coding device names.
Output modes
By default, serve-sim prints human-readable status to stdout. For agent loops, prefer JSON output:
npx serve-sim --list -q # JSON array of running streams
npx serve-sim --detach -q # JSON with pid/port/url after spawn
npx serve-sim camera status -q # JSON with {alive, source, mirror, ...}
Parse -q output programmatically. Never parse the non--q human output — it can change between versions.
Showing the stream in your agent's preview
When the user asks to "see the simulator here", "view it in preview", "open it in this tool", or similar, the goal is to stream the simulator into the same surface the user is chatting with. serve-sim returns a regular HTTP URL — the agent's job is to surface that URL and, if the host exposes a preview tool, hand it off.
Steps:
-
Start serve-sim and capture the URL:
npx serve-sim --detach -qThis returns JSON like
{"pid":..., "port":3200, "url":"http://localhost:3200", "streamUrl":"http://localhost:3100", ...}. Theurlfield is the human-facing preview UI;streamUrlis the raw MJPEG endpoint. -
Always surface the URL plainly in your response so the user can fallback to opening it manually in any browser.
-
Probe your host's preview tool and hand off the URL if one exists. Examples of tool names you may see in your toolset:
preview_start(Claude Code) — call it with{ url: "<url>" }.mcp__Claude_Preview__preview_start(some MCP setups).- A
browser_open,open_url, or similar URL-opening tool — pass the URL. - Cursor / Codex CLI / others may not expose a preview tool to the agent. In that case, just print the URL and tell the user how to open it (their browser, their IDE's built-in browser pane, etc.).
-
Do not assume any specific preview tool exists. Inspect the tools available to you in the current session. If one matches the description above, use it. If none does, fall back to step 2 (print the URL prominently).
The stream stays alive until npx serve-sim --kill. Multiple clients (the host's preview + the user's browser + a tunnel) can read the same URL simultaneously.
See references/workflows.md workflow "Show the simulator stream in the host's preview" for the full recipe.
Workflows
For complete end-to-end recipes (UI automation, camera testing, accessibility-driven taps, deep-link flows, preview handoff), see references/workflows.md. The reference covers the patterns documented in serve-sim's own AGENTS.md.
Cleanup
Always stop helpers when finished, unless the user explicitly wants them to keep running:
npx serve-sim --kill # stop all
npx serve-sim --kill "iPhone 16 Pro" # stop one
Orphan helpers occupy ports 3200/3100 and prevent fresh starts.
Anti-patterns
- Do not pass pixel coordinates. All coords are normalized
0..1. If the user gives pixel values, divide by the screen dimensions reported byGET /config. - Do not use
gesturefor plain taps. Usetap. See "Critical gotcha" above. - Do not assume
npx serve-simis already running. Verify with--listor by checking$TMPDIR/serve-sim/server-{udid}.json. If absent, start it explicitly. - Do not skip the prerequisites check on the first invocation in a session. Wrong macOS version, missing Xcode CLI tools, or Node <18 produce confusing errors downstream.
- Do not invent button names. Only these six are valid:
home,swipe_home,app_switcher,lock,siri,side_button. See references/buttons-rotation.md for the source-of-truth list. - Do not parse the non-quiet human output. Use
-qfor JSON. - Do not leave camera helpers running across unrelated tasks. Stop them with
npx serve-sim camera --stop-webcamwhen done. - Do not guess coordinates when an accessibility lookup returns no match. If you fetched the AX tree (e.g.
GET /ax) to find a target element and the query returned no result, fail loudly — tapping a guessed spot is almost always worse than reporting "target not found" back to the user. See references/workflows.md workflow 1 for the guard pattern.
Reference index
- references/gestures.md — exact gesture JSON shapes, edge values, multi-touch, drag/swipe recipes.
- references/buttons-rotation.md — the six valid buttons and the four orientations, with behavioral notes.
- references/camera.md — synthetic camera injection: placeholder, file, webcam, mirror modes, hot-swap.
- references/permissions.md — granting/revoking app privacy permissions, including push notifications.
- references/ca-debug.md — the five CoreAnimation debug flags and when each one helps.
- references/endpoints.md — HTTP and WebSocket endpoints for agents that bypass the CLI.
- references/workflows.md — end-to-end recipes for UI automation, camera testing, deep-link flows.
Frequently asked questions about Serve Simulator
Similar skills
Android App Development
Comprehensive guide for Android and cross-platform app development.
Add App Clip to Expo App
Integrate lightweight iOS App Clips into your Expo project.
APK Reverse
Streamline your Android APK reverse engineering process.
Swift Expert
Master iOS/macOS development with Swift and SwiftUI.
React Native Expert
Build and optimize mobile apps with React Native and Expo.
Kotlin Specialist
Master idiomatic Kotlin with expert patterns and practices.
