RocketSim: a toolbelt for the Xcode iOS Simulator

What RocketSim solves for iOS Simulator work

The Xcode Simulator is a capable runtime with an awkward control surface. Inspecting state, triggering a flow, grabbing a screenshot or a recording, and checking accessibility elements each mean a different detour, and repeating any of those steps by hand does not scale. RocketSim's stated purpose is to make those common Simulator workflows easier to inspect, automate and repeat. The repository frames it as an enhancement to the Simulator rather than a replacement for Xcode: it sits alongside the tools an iOS developer already uses.

The audience is narrow and specific. This is a macOS product for people building iOS apps, and the README lists the workflows it targets: inspecting and debugging simulator behaviour, triggering app actions and test flows without leaving the coding environment, capturing screenshots and recordings with less manual work, and automating simulator interaction through the RocketSim CLI. A backend engineer or an Android developer gets nothing from it. If you do not run the Xcode Simulator, the tool has no surface to attach to.

One claim in the repository description is worth separating from the code. The description says the app is used by 80k+ developers. That is a marketing figure carried in the repository metadata, not something the repository itself demonstrates, and it should not be read as a measure of code quality or project health.

How the agent skill and RocketSim CLI fit together

The most concrete mechanism described in the README is the RocketSim Agent Skill. Its job is to give AI coding tools a reliable way to work with the iOS Simulator through RocketSim. The flow the README describes has three parts.

First, the skill detects the installed RocketSim version. Second, it uses the matching RocketSim CLI, so the automation layer tracks whatever build is on the machine rather than pinning to a separate version. Third, it lets an agent inspect what is visible on screen before interacting with the app. The README's phrasing is that this gives agents eyes: instead of guessing with brittle simulator automation, the agent reads the current UI state and then acts, using what the README calls the same stateful tooling that powers RocketSim itself.

The listed agent capabilities are navigation and testing of Simulator apps, reading visible accessibility elements before interacting, and tapping, typing, swiping and triggering flows. The ordering matters. Reading accessibility elements is presented as a precondition for interaction, which is a different design from coordinate-based automation that taps blind and retries on failure.

That skill no longer lives in this repository. The README states it has moved to its own repository, RocketSim-Agent-Skill, with installation instructions, packaging metadata and a release workflow. Anyone reading this repository expecting to find the skill source will not find it here.

Installing RocketSim and running a first agent-assisted flow

This repository does not contain installation steps. It is the project's GitHub home, and its README points outward for everything practical: the RocketSim website for the product, the documentation site for feature guides and setup help, and the Mac App Store listing for the app itself. The top-level entries confirm the shape of the repository: Assets, CHANGELOG.md, LICENSE, README.md, a RocketSimFeatures.playground directory and docs.

So the install path starts at the Mac App Store listing linked from the README. Once the app is installed, the agent skill is the part you set up from the other repository, which the README says carries full installation instructions and packaging metadata. The README does not reproduce those steps here, so treat the RocketSim-Agent-Skill repository as the source of truth rather than guessing at commands.

What the README does describe is the behaviour you should expect after setup. The skill detects the installed RocketSim version and selects the matching RocketSim CLI, then exposes Simulator interaction to your agent. A first real use is the loop the README names: have the agent read the visible accessibility elements, then tap, type or swipe based on what it read, then trigger a flow and check the result. If the agent is acting on stale screen state, the version detection or the CLI pairing is the first thing to check, because the README ties the two together explicitly.

Because the README gives no literal command, no package name and no environment variable for the CLI, there is nothing to quote in a code block without inventing it. The honest first step is the documentation site and the skill repository, in that order.

Where RocketSim is the wrong tool

The clearest limitation is scope. RocketSim enhances the iOS Simulator. It is not a device farm, it does not replace Xcode, and nothing in the README suggests it covers Android, web or cross-platform targets. Teams that need one automation layer across several platforms will end up maintaining RocketSim for iOS and something else everywhere else.

The second limitation is structural and visible in the repository layout. The agent skill has been split into a separate repository. That is a reasonable packaging decision, but it means the README here is a pointer rather than a manual. A reader who wants to know exactly which CLI subcommands exist, which flags they take, or how version detection resolves a mismatch will not find those answers in this repository. The README does not document rollback, error handling or what happens when the installed RocketSim version and the CLI do not line up; it only says the skill uses the matching CLI.

The third is distribution. RocketSim is distributed through the Mac App Store, and the repository does not carry a source build path for the app. There is a RocketSimFeatures.playground directory, which suggests the repository is used for feature work and documentation rather than as the shipping artifact. If your constraint is that every tool in your stack must be buildable from source you control, this is not that tool.

Finally, the release history in the repository is old relative to the project's activity. The most recent release listed is 5.0.0 from 2021-08-13, with 3.4.3 and 3.4.1 before it in 2021. The repository's last push was on 2026-09-10, so work is happening, but the tagged releases here do not reflect it. Anyone who reads release tags as a proxy for current capability will draw the wrong conclusion.

How RocketSim differs from Xcode command line tooling

The natural comparison is Xcode's own command line tools, particularly simctl, which Apple ships for controlling simulators from a shell. The difference in approach is the layer each one operates at.

simctl manages simulators as devices: booting, installing, launching, and taking screenshots at the device level. It has no concept of what is on screen beyond a pixel buffer, and no built-in notion of accessibility elements as a readable interface. RocketSim's agent skill, as the README describes it, is built around reading visible accessibility elements before interacting and then tapping, typing and swiping in response. That is a state-aware loop rather than a device-control loop, and it is the reason the README contrasts it with what it calls brittle simulator automation.

The second difference is packaging. simctl ships with Xcode and costs nothing extra; RocketSim is a separate Mac App Store product with its own versioning, and the agent skill is a third repository on top. You are trading a dependency you already have for a layer that adds inspection, capture and accessibility tooling in one place, plus an automation path designed for agents. Whether that trade is worth it depends on how much time your team currently loses to manual Simulator work and hand-rolled scripts.

A third difference is who the automation is for. simctl scripts are written by engineers and read by engineers. The RocketSim Agent Skill is explicitly aimed at AI coding tools, with the version detection and CLI pairing handled by the skill itself. If you are not running an agent against your simulator, that part of the product does nothing for you.

Maintenance, licensing and what the repository does not say

The repository is not archived, and its last push was on 2026-09-10, which is recent. That tells you commits are landing, but it does not tell you what is in them. The release tags here stop at 5.0.0 in 2021, so the CHANGELOG.md file in the repository root is the better place to look for what has changed since, and the documentation site is where feature-level guidance lives.

The upgrade surface is unusual because the product is distributed through the Mac App Store. Version management for the app itself is largely handled by the store, and the README's description of the agent skill detecting the installed version and using the matching CLI suggests the CLI is expected to track the app rather than be pinned independently. That is convenient when it works and opaque when it does not, since the README does not describe a fallback when no matching CLI is found.

On licensing, the repository's licence identifier is NOASSERTION. GitHub uses that when it cannot match the LICENSE file to a known licence template. The repository contains a LICENSE file, but its terms are not summarised in the README, and nothing here states whether the app, the CLI or the agent skill are open source, source-available or commercial. If licence terms matter to your organisation, read the LICENSE file directly and check the Mac App Store listing, because the repository metadata alone will not answer the question. That is a factual gap, not legal advice.

Support runs through two channels the README names: GitHub issues for bugs and feature requests related to RocketSim, and the documentation site for feature guides and setup help.

Editorial conclusion

RocketSim suits iOS developers who already live in the Xcode Simulator and want inspection, capture and scripted interaction in one place, and it suits teams wiring an AI coding agent to a real simulator through the RocketSim CLI. It is not for Android or cross-platform work, it is not a replacement for Xcode, and anyone who needs the Simulator without Xcode will not find that here. Before adopting it, open the documentation site for the current feature list, confirm the RocketSim CLI version your install ships, and check the RocketSim-Agent-Skill repository for the installation steps the main README does not carry.

Frequently asked questions

Official sources

1. AvdLee/RocketSimApp on GitHub
2. Issues
3. Project website
4. README
5. Releases