Claude Code Integrates Live iOS Simulator

Available in public beta for Pro, Max, and Team plan users running Claude Code Desktop v1.24012.0 or later, this update feels like a massive leap forward. The AI model can now actually see your application as it runs, click through the interface, and iterate on code changes in real time. You just sit back and watch the magic happen in a dedicated simulator pane right next to your active chat.

It is honestly hard to overstate how much time this will save developers building complex UIs. While the AI does the heavy lifting, you can still manually tap and swipe within the simulator, with full support for standard Apple Simulator shortcuts.

Setup Requirements and System Eligibility

Unsurprisingly, since Apple's iOS Simulator is strictly tied to macOS, this new capability is exclusively a Mac feature. You will need Xcode installed on your machine, properly configured with the necessary iOS platform components.

During the initial launch, the desktop app will ask you to grant Claude device access. Once authenticated, Claude goes full autopilot—installing the compiled app, navigating the UI, and reading the screen to verify the exact changes it just coded.

Architectural Differences: Desktop App vs. CLI

Under the hood, Anthropic built two distinct ways for Claude to drive the simulator, depending on your preferred interface. In the desktop app, the embedded pane hooks into the Apple simulator directly.

This direct pipeline is brilliant because it bypasses the need for sweeping "computer use" permissions. The simulator pane lives peacefully alongside your workflow, never hijacking your main screen or burying your other windows.

Things work differently if you prefer the CLI. When running from the command line, Claude accesses the iOS Simulator via the broader computer use capability. It actually takes over to control the simulator on your screen, clicking and dragging exactly like a human would.

Session Constraints and Security

There is one major catch: this only works locally. Cloud and SSH sessions simply cannot reach the simulators hosted on your local Mac hardware.

While slightly annoying for remote-first developers, this restriction makes complete sense for security. It keeps simulator access strictly confined to the host machine where your Xcode and project files physically live.