From the Macswarm team. Originally published at macswarm.com . Macswarm is currently accepting early-access requests.

Why an agent needs a Simulator it can see

An iOS change is not finished when it compiles. Someone has to launch the app, tap to the screen that changed, read the log and look at the result. When the agent makes the change, the agent has to be the one looking. On a developer's own Mac this is routine: Xcode provides the Simulator, and Claude Code Desktop opens an iOS Simulator pane next to the conversation when Claude builds, installs, launches or checks the app.

That pane does not travel. Claude Code's documentation says the Simulator pane is "available in local sessions only": in cloud and SSH sessions, Claude runs on a machine that cannot reach the Simulators on your Mac. Any agent in a hosted Linux sandbox is in the same position: it can edit and build a project, but there is no macOS, no Xcode and no Simulator in the box.…