RocketSimApp is a GitHub issue tracker for a closed-source Mac app
RocketSim — 30+ tools for Xcode's iOS Simulator. Testing, debugging, network monitoring, captures, accessibility, app actions, and AI agent automation via the RocketSim CLI. Used by 80k+ developers.
At a glance
- What is it?
- The AvdLee/RocketSimApp repository is not the simulator tool itself. It is the public front door for RocketSim, a paid Mac App Store app, and the README points elsewhere for installation and the agent skill. Here is what the repository actually contains and what you can and cannot do with it.
- Who is it for?
- Adopt RocketSim only if you are willing to take a proprietary Mac App Store dependency: install it from the App Store link in the README, then verify the current CLI surface and agent skill installation instructions at rocketsim.app/docs and in the separate RocketSim-Agent-Skill repository, because this repository ships no code to inspect.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What the RocketSimApp repository is, and what it is not
The name invites a wrong assumption. AvdLee/RocketSimApp sounds like the source of RocketSim, the tool that adds debugging, capture and accessibility features to Xcode's iOS Simulator. The README does not support that reading. It describes RocketSim as a product with a website, a documentation site and a Mac App Store listing, and it frames this GitHub repository as the place to "Open a GitHub issue for bugs or feature requests related to RocketSim." There is no build instruction, no Xcode project description, no installation section for the app itself. The primary language is listed as Swift, but nothing in the supplied material shows which Swift sources live here or whether they compile into anything a user runs. Treat the repository as a support and issue channel attached to a commercial macOS application, not as a distributable.
That distinction matters more than it usually would. A developer scanning topics like ios, testing and debugging might clone this expecting to read the implementation of the network monitor or the accessibility inspector. The material gives no indication that those implementations are present. The single code-adjacent artefact the README does name, the agent skill, has been moved out to a separate repository, AvdLee/RocketSim-Agent-Skill, which the README says holds "full installation instructions, packaging metadata, and release workflow." So the one piece a reader might reasonably hope to inspect or adapt is explicitly not here.
The problem RocketSim targets, and who the README says it is for
The stated problem is workflow friction inside the iOS Simulator. According to the README, RocketSim "enhances the iOS Simulator with tools for testing, debugging, captures, accessibility, app actions, and more," and the goal is to make "common Simulator workflows easier to inspect, automate, and repeat." The audience is iOS developers who already spend their day in Xcode and want simulator inspection, app actions and screenshots without switching context. The README frames the benefit as moving faster by staying inside "their coding environment."
The more specific audience is the one added by the agent skill. The README argues that AI coding tools interacting with the Simulator currently rely on "brittle simulator automation" that guesses at UI state. RocketSim's answer is to let an agent "inspect what is visible on screen before interacting with the app," with the README summarising the effect as giving agents "eyes." The listed agent use cases are narrow and concrete: navigate and test Simulator apps, read visible accessibility elements before interacting, tap, type and swipe, and reuse the RocketSim version already installed on the machine. If your work is manual simulator debugging, the first paragraph applies to you. If your work is wiring an agent into a test loop, the second does.
How the agent skill mechanism is described
The README gives a three-part mechanism rather than a diagram. First, the skill "detects the installed RocketSim version" on the machine. Second, it "uses the matching RocketSim CLI," so the agent drives the version you already have instead of a bundled or pinned one. Third, it enables the agent to "inspect what is visible on screen before interacting with the app," which is the step the README contrasts with guessing.
The interaction model is described as stateful: agents "interact with it efficiently using the same stateful tooling that powers RocketSim itself." That phrasing implies the CLI is not a thin screenshot wrapper but exposes the same session state the app uses, so a tap or a swipe is issued against a known UI state rather than a fresh snapshot each time. The README does not specify the transport, the command names, or how state is scoped between calls. It also does not say whether the skill talks to the Simulator through Xcode's own tooling or through a private RocketSim interface. Those are the questions to answer from the documentation site before designing an agent loop around it, because the version-matching behaviour means an upgrade on one side can change what the other side sees.
The README is explicit that the skill no longer lives in this repository. Installation instructions, packaging metadata and the release workflow are all in AvdLee/RocketSim-Agent-Skill. Anything about how the skill is packaged, versioned or released has to be read there, not here.
Getting it running: the paths the README actually gives
There is no install command in the supplied material. The README routes installation and setup to three canonical resources: the website at https://www.rocketsim.app, the documentation at https://www.rocketsim.app/docs, and the Mac App Store listing at https://apps.apple.com/us/app/rocketsim-for-xcode-simulator/id1504940162. A Mac App Store identifier is a distribution channel, not a package manager, so the practical setup path is to install the app from that listing and then follow the documentation site for feature guides. The README says to "Use the documentation site for feature guides and setup help," which is the closest thing to a setup instruction it contains.
For the agent skill, the README says the separate repository holds "full installation instructions." That is the only pointer. There is no config key, no environment variable and no CLI invocation quoted anywhere in the material provided, so any command you see in a tutorial that is not sourced from rocketsim.app/docs or from the agent skill repository should be treated as unverified. If you need a reproducible setup for a team, the absence of a scripted install in this repository is itself the finding: provisioning goes through a consumer app store account, not a lockfile.
The licence question the repository does not answer
The repository metadata reports the licence as NOASSERTION. That is not a licence. It means the automated classifier could not match what it found, or found nothing, to a known licence identifier. The README does not carry a licence section, and the supplied material does not describe a LICENSE file. Meanwhile the product is distributed through the Mac App Store, which implies terms attached to that listing rather than terms attached to this repository.
The practical consequence is that you cannot reason about RocketSim's usage rights from the GitHub page. If your organisation has a policy that requires an OSI-approved licence before a tool enters the build or test pipeline, this repository will not satisfy it, and the Mac App Store listing is where the applicable terms live. I am not giving legal advice here; the point is narrower. The licence field on this repository is uninformative, and anyone treating the presence of Swift in the language breakdown as evidence of open source would be reading something into the metadata that is not there.
Limitations, and the case where this is the wrong tool
The clearest limitation is the one already stated: the repository is not the product. If your requirement is to read, fork, patch or self-host the simulator tooling, this repository does not meet it, and the README gives no indication that it ever will. The agent skill, the one component with a plausible open packaging story, is deliberately elsewhere.
A second limitation is version coupling. The skill "detects the installed RocketSim version" and "uses the matching RocketSim CLI." That design keeps the agent aligned with the app, but it also means the agent's behaviour is a function of what each developer has installed. On a team where machines drift across RocketSim versions, an agent flow that works on one laptop is not guaranteed to behave identically on another. The README does not describe a pinning mechanism, so this is a real operational question rather than a hypothetical one.
A third is scope. The README lists testing, debugging, captures, accessibility, app actions and network monitoring as topics, but the material does not describe any of those features in detail. Anyone evaluating RocketSim for one specific capability, say network monitoring, gets nothing from this repository to judge it on and has to go to the documentation site. And if your target is not the iOS Simulator, none of this applies: RocketSim is explicitly built around Xcode's simulator, and the README offers no path for physical devices or other platforms.
The alternative: Xcode's own simulator tooling and UI automation
The obvious comparison is the toolchain Apple already ships. Xcode includes the Simulator itself, and XCUITest drives it through the accessibility layer with a scripting interface that is part of the standard test target. The difference in approach is architectural. XCUITest is a test framework: you write assertions against elements and the runner owns the session, which makes it good for regression suites and poor for ad hoc, exploratory interaction. RocketSim, as described, is interactive tooling: a human or an agent inspects the current UI state and then acts on it, with the README contrasting that against "brittle simulator automation" that guesses.
That contrast is the honest way to choose. If you need a deterministic suite that runs in CI and fails the build, XCUITest plus the stock Simulator is the lower-dependency option, and it costs nothing beyond what you already have. If you need a person or an agent to look at a running app, read the visible accessibility elements and then tap or type, the README's description of RocketSim addresses a gap XCUITest does not try to fill. The trade is that you take on a proprietary Mac App Store dependency and a version-matching CLI, where the Apple route keeps you inside the Xcode toolchain you already maintain. Neither is strictly better; they answer different questions.
Maintenance and upgrade cost
The releases listed in the material are old and do not match the current product. The most recent is 5.0.0, dated 2021-08-13, followed by 3.4.3 in March 2021 and 3.4.1 in February 2021. The repository's last push is 2026-09-10. Read together, those dates suggest the release tags here are not how RocketSim is currently shipped, and that the Mac App Store listing is the real distribution channel. Do not read the release list as a changelog for the app you would install today.
Upgrade cost therefore sits with the app, not with a package manager. There is no dependency file in this repository to bump and no version pin to review in a pull request. Updates arrive through the App Store, and the agent skill follows the installed version by design. The maintenance question to ask is not how often this repository changes but how your team keeps RocketSim versions aligned across machines, since the skill's behaviour depends on that alignment. The README offers no mechanism for it, so it is a process question you have to answer yourself before rolling the agent skill out widely.
Editorial conclusion
Adopt RocketSim only if you are willing to take a proprietary Mac App Store dependency: install it from the App Store link in the README, then verify the current CLI surface and agent skill installation instructions at rocketsim.app/docs and in the separate RocketSim-Agent-Skill repository, because this repository ships no code to inspect. Do not clone AvdLee/RocketSimApp expecting to build, patch or self-host the tool; the README directs bugs and feature requests here as issues, and that is the extent of what this repository gives you. Before committing a team to it, confirm the licence terms shown on the Mac App Store listing, since the repository metadata reports NOASSERTION and no licence file is described.
Community notes