Simulator Monitor

Boot, stop, or restart an iOS simulator without opening Xcode

Room Service keeps running iOS, tvOS, and Android simulators in the menu bar. Launch one, stop it, restart it, or copy its name and UDID in two clicks.

Room Service keeps running iOS, tvOS, and Android simulators in the menu bar. Launch one, stop it, restart it, or copy its name and UDID in two clicks.

Room Service keeps running iOS, tvOS, and Android simulators in the menu bar. Launch one, stop it, restart it, or copy its name and UDID in two clicks.

Simulators in Room Service

You want an iPhone 16 simulator up to check a screen. The options are to open Xcode and wait for a build, dig through Simulator’s File > Open Simulator menu, or run xcrun simctl list devices, copy a UDID, and xcrun simctl boot it. Stopping is the same in reverse: simctl shutdown, or quit Simulator and hope the device shut down with it. The Android emulator has its own window, its own CLI, and its own way of hanging around.

Room Service lets you boot an iOS simulator without Xcode, from the menu bar. The same list shows what is running right now, tvOS simulators and Android emulators next to the iPhones and iPads, with a Stop button on each row.

Every simulator on your Mac, in the menu bar

What is booted, right now. The Simulators section of the menu bar popover lists every booted iOS and tvOS simulator and every running Android emulator, grouped by platform, with a count in the header. Each row shows the device name and its runtime, for example iOS 18.1, or the emulator serial such as emulator-5554. The menu bar icon’s tooltip adds “2 active simulators” to its summary.

Launch any device you have installed. The plus button opens a picker grouped into iPhone, iPad, Apple TV, and Android. Devices with more than one runtime installed show as one row, iOS 18.1 + 2 more, and expand so you pick the version. Room Service boots the device with simctl and brings Simulator to the front, or starts the Android emulator with the AVD you chose.

Stop or restart in one click. Stop sends simctl shutdown to that device, or adb emu kill to that emulator. Restart is a shutdown followed by a fresh boot of the same device and runtime. The row dims with a spinner until the device is gone, and a toast confirms it.

Copy the name or the ID. The gear menu copies the device name or its identifier: the UDID for an Apple simulator, the AVD name for Android. Paste it into xcrun simctl, a test script, or a CI config without listing devices first.

Know when one starts. A macOS notification tells you when a simulator boots, whether you started it from Room Service, Xcode, or a script. Turn it off in Settings > Alerts.

Your coding agent sees the same list. Over Room Service’s MCP server, Claude Code, Codex, or Cursor can call list_simulators, start_simulator, stop_simulator, and restart_simulator on the same devices, through the same commands.

How to manage iOS simulators from the menu bar

  1. Open the popover. Click the Room Service icon in the menu bar and scroll to Simulators. While Simulator or the emulator is open the list refreshes every 3 seconds, otherwise every 30, or on the refresh button.

  2. Boot one. Click the plus button, pick iPhone, iPad, Apple TV, or Android, then the device. Expand a row to choose the runtime. It appears in the running list a moment later.

  3. Stop or restart. Click Stop on the row, or open the gear menu for Restart. Both act on that one device and report back with a toast, or an error if simctl or adb refused.

  4. Grab the details. Copy name or Copy ID puts the value on your clipboard and shows what was copied.

What it will and will not do

  • Stop is a normal simctl shutdown or adb emu kill. Apps running inside the simulator are closed; the device, its installed apps, and its data are kept. Nothing is erased or deleted.

  • Each action targets one device by UDID or AVD name. There is no “shut down all” button and no action touches a simulator you did not click.

  • Only available devices are listed. Simulators whose runtime is missing (isAvailable: false in simctl) do not appear. watchOS and visionOS simulators are not supported yet.

  • Apple simulators need Xcode (xcrun simctl). Android emulators are found through ANDROID_SDK_ROOT, ANDROID_HOME, or ~/Library/Android/sdk; without adb, running emulators cannot be detected or stopped.

  • Over MCP, list_simulators is read-only. start_simulator, stop_simulator, and restart_simulator sit in the “Scan, simulators, and suggestions” group in Settings > Agents, on by default once you allow agents to connect. Each call waits up to about ten seconds for the device to reach the new state, and lands in the Ops Feed with the agent’s name.

  • Simulator storage is a separate feature. The Xcode cleanup category lists each simulator device, runtime image, and volume as its own row, none selected by default, and a booted device is refused until you shut it down.

Free vs Pro

All of it is free: the menu bar list, Launch, Stop, Restart, Copy name, Copy ID, the start notification, and the four MCP tools. Cleaning simulator data in the Xcode category needs Pro, as every cleanup does.

Frequently Asked Questions

How do I boot an iOS simulator without opening Xcode?

How do I stop an iOS simulator from the menu bar?

Is this the same as `xcrun simctl shutdown all`?

Does it work with the Android emulator?

Can I see a simulator’s UDID without running `simctl list`?

Can Claude Code or Cursor start a simulator for me?

Explore more of Room Service