Verdict: Claude Code Desktop's new iOS Simulator panel — launched July 21, 2026, in public beta — lets an AI coding agent build, launch, visually inspect, and fix your iOS app inside the simulator without a single manual build step. It is the most significant step toward closed-loop AI testing for mobile development to date, and it works on Pro, Max, and Team plans but is conspicuously absent from Enterprise. If you build iOS apps and use Claude Code, this feature closes the gap between "the code looks right" and "the screen looks right."
Last verified: 2026-07-30 · Status: Public beta · Platform: macOS only · Plans: Pro, Max, Team (not Enterprise)
- The panel opens automatically when Claude runs your app — no command or setting to toggle.
- It drives the simulator directly, not through screen capture, so it works without macOS Accessibility or Screen Recording permissions.
- Up to 4 simulator panes per session; each session gets its own device.
- Use test accounts, not real ones — screenshots are sent to Anthropic per normal conversation retention.
- Local sessions only: cloud and SSH sessions can't reach your Mac's simulators.
What Is the Claude Code iOS Simulator Panel?
The iOS Simulator panel is a built-in view in Claude Code Desktop that streams Apple's iOS Simulator live alongside your conversation. When you ask Claude to build, run, or check an iOS app, it launches the app in a simulated iPhone or iPad, watches the screen in real time, reads what it sees, and fixes issues — all inside the same session where it wrote the code.
This is a fundamental shift from how AI coding agents traditionally work. Before, the agent wrote code and hoped the result matched the intent. Now it can see the result and iterate, creating a closed build-run-look-fix loop. Claude installs the app, taps through screens, reads the rendered UI, identifies broken layouts or missing buttons, and patches the Swift or SwiftUI code — often before you've touched your keyboard.
The key technical distinction: the panel communicates directly with Apple's Simulator tooling (the same simctl infrastructure Xcode uses), not through "computer use" — Anthropic's general-purpose screen-control feature that moves a virtual mouse around your desktop. Because the panel drives the simulated device natively, it never takes over your screen, never hides your other windows, and does not require the macOS Accessibility or Screen Recording permissions that computer use needs.
What Are the Requirements to Use It?
You need three things before the panel will work, and all three are non-negotiable:
Claude Desktop v1.24012.0 or later. The iOS Simulator panel is not available in older versions of the desktop app, nor in the CLI. If you've been running Claude Code purely from the terminal, you'll need the Mac desktop application. Check for updates under Claude > Check for Updates and restart after updating.
A Mac. Apple's iOS Simulator is macOS-only — there is no Linux or Windows path. The desktop app does not ship with Apple's simulator tooling, so the simulator runtime lives entirely in your Xcode installation.
Xcode with the iOS platform installed. Download Xcode from the Apple Developer site. After installing, open Xcode at least once so it downloads the iOS simulator runtime. If the runtime is missing, the panel shows a setup checklist and you can install it manually by running
xcodebuild -downloadPlatform iOSin your terminal, or by downloading the runtime from Xcode's Settings > Components tab.
You also need to be on the right plan (see below), and you must be in a local session — not a cloud or SSH session. In cloud and SSH sessions, Claude runs on a remote machine that cannot reach the simulators attached to your Mac. This is the most common silent failure: everything looks configured correctly, but the panel never appears because you started a cloud session by default.
Which Claude Plans Get the iOS Simulator Panel (and Which One Doesn't)?
The iOS Simulator panel is available on Pro ($20/month), Max ($100–$200/month), and Team ($25–$125/seat/month) plans. It is not available on the Enterprise plan. This is the detail that most coverage of the launch skipped over — and it's buried in a note near the bottom of Anthropic's official documentation.
| Plan | Price | iOS Simulator Panel | Claude Code Access |
|---|---|---|---|
| Free | $0 | No | No |
| Pro | $20/mo | Yes (public beta) | Yes |
| Max 5x | $100/mo | Yes | Yes |
| Max 20x | $200/mo | Yes | Yes |
| Team Standard | $25/seat/mo | Yes | Standard seats only |
| Team Premium | $125/seat/mo | Yes | Yes |
| Enterprise | Custom | No | Yes (with managed controls) |
Sources: Anthropic Claude Code docs, Claude pricing page.
Why Enterprise is excluded: Enterprise plans come with managed security policies, custom data retention, and compliance requirements (SSO, audit logs, SCIM provisioning). The iOS Simulator panel sends screenshots of the simulated device to Anthropic's servers for processing — those screenshots are retained per the conversation's retention settings. For organizations with strict data handling agreements, this data flow likely couldn't satisfy Enterprise compliance requirements at launch. If your company runs an Enterprise plan, check with your Anthropic account representative — the exclusion may change as the feature moves from beta to general availability.
There are also two managed settings that can block the feature even on plans that support it: disableMobileSimulatorTools removes Claude's simulator tools while leaving the panel usable for your own manual testing, and requireCoworkFullVmSandbox runs all tools in an isolated virtual machine, which disables the panel entirely.
How Do You Start a Session With the iOS Simulator?
There is no command to learn and no setting to switch on. The panel opens by itself when Claude acts on a request to run your app. Here are the steps that get it working on the first try:
Open the Code tab in Claude Code Desktop. Start a new session with your iOS app's project folder as the project root. Any Xcode project or Swift Package that builds for the iOS Simulator target works — UIKit, SwiftUI, or anything in between.
Phrase your request around running or checking the app, not just writing code. The single most common failure is asking something like "fix the login bug" — Claude fixes the code but never launches the simulator because you didn't ask it to run anything. Instead, say: "Build the app and run it in the simulator, then tap through the sign-up flow and tell me what you see." The panel only opens when Claude detects a run or verify instruction.
Grant one-time device access on first use. The first time Claude controls a particular simulated device, the desktop app prompts you to allow it. This consent covers device control and screenshot capture, and it's granted once per device — not once per session. If you decline, the device still boots and the panel still shows it, but Claude's taps and screenshots stay off. Change your mind later by clicking the "Let Claude use it" button.
Watch the panel open automatically. When Claude builds and launches your app, the simulator pane appears next to the conversation, streaming the device screen live. You'll see a "Claude is using this device" badge when Claude is actively controlling the device — wait for it to clear before tapping yourself.
Manually open the panel if needed. Once your session has a simulator device attached or has edited Swift files, the Views menu in the session toolbar shows an "iOS Simulator" entry. Click "Attach Simulator" or pick a specific device from the Device menu — picking a shut-down device will boot it.
What Can You Do Inside the Simulator While Claude Works?
The panel is fully interactive. You and Claude drive the same simulated device, which means you can tap and swipe while Claude is also working — but you should wait for the "Claude is using this device" badge to clear before you interact, or you'll be testing your own finger instead of the app.
| Action | Shortcut | Notes |
|---|---|---|
| Tap or swipe | Click and drag on device screen | Same as Apple's Simulator app |
| Home button | Cmd+Shift+H | Returns to the device home screen |
| Lock device | Cmd+L | |
| Volume up / down | Cmd+Up / Cmd+Down Arrow | |
| Rotate device | Cmd+Right Arrow | Quarter-turn clockwise |
| Screenshot | Cmd+S | Saves to your Desktop |
| Screen recording | Cmd+R | Saves to your Desktop — no capture software needed |
| Switch devices | Device menu | Shows OS version and boot status for each |
| Detach device | Detach button | Stops streaming without shutting down |
Below the device screen, a row of stream settings lets you adjust the video feed your Mac is rendering: frame rate, resolution, encoding (H.264 or JPEG), and an FPS readout. If the panel is slowing down your Mac — especially on older machines — turn the resolution and frame rate down before you blame the feature. Importantly, these settings change how the panel displays the device; they do not affect how your app runs.
Specify a device for layout testing: If you want to test on a specific form factor, name it in your prompt. Say "Run it on the iPhone SE simulator" and Claude targets that device when it builds and launches. This is valuable for catching layout breakage on small screens — small phones clip content that looks fine on a standard 6.1-inch display.
How Does Session Device Management Work?
Each session gets its own simulated device; two parallel sessions never share one. When you switch between sessions in the sidebar, the simulator view switches with the conversation and resumes where it left off when you switch back. If Claude works with more than one device in a session, each opens its own panel — up to four simulator panes per session.
Claude also cleans up after itself:
- Simulators that Claude booted shut down automatically when you quit the app, archive the session, or 10 minutes after you detach a device.
- Devices that you booted (via the panel or Apple's own Simulator app) are never shut down automatically.
- You can manually shut down any device from the panel.
This design means you can leave a session running, come back later, and pick up on the same device state — but if Claude started the device, don't expect it to be there after a 10-minute idle.
What Are the Privacy and Security Implications?
This is the part of the update that deserves real attention — and the part the announcement clips left out.
Claude's screenshots of the simulated device are sent to Anthropic. They are retained under the same conversation retention settings that apply to your chat history. This means: if your plan retains conversations for 30 days, screenshots are also kept for 30 days. If you're on a plan that retains them longer, screenshots are kept longer too.
The practical implication: do not sign in to real accounts on a device that Claude is using. Use test accounts with test credentials and test API keys. A simulated device that Claude can screenshot and upload is not the same as a private device on your desk — the screen contents leave your machine. Anthropic states this directly in their documentation: screenshots are sent to Anthropic and kept per standard conversation retention settings.
Two specific actions follow your session's permission mode (separate from the one-time device consent):
- Opening a URL on the device — because a URL can carry data off the simulated device via deep links or Safari.
- Building the app — because
xcodebuildruns your project's build scripts on your actual Mac, which could include arbitrary scripts.
Both of these will prompt you per your session's permission settings, not the one-time device consent.
How Is This Different From Computer Use?
Claude Code has had "computer use" — a feature where the AI controls your Mac's screen by moving a virtual mouse and keyboard — since earlier in 2026. The iOS Simulator panel is architecturally distinct:
| Feature | iOS Simulator Panel | Computer Use |
|---|---|---|
| Control mechanism | Direct simctl integration |
Virtual cursor / keyboard events |
| Scope | Only the simulated device | Your entire macOS screen |
| macOS Accessibility permission | Not required | Required |
| Screen Recording permission | Not required | Required |
| Takes over other windows | No | Yes |
| Available from CLI | No — reaches simulator through computer use instead | Yes |
From the CLI (terminal), Claude reaches the iOS Simulator through computer use — it moves the cursor around the simulator window the way you would with a mouse. The desktop panel is the native path that skips both screen capture and macOS permissions entirely.
If you're comparing this to other agentic coding setups, the iOS Simulator panel is closest in spirit to a purpose-built testing tool — but it runs inside the same agent that writes the code.
What Practical Workflows Does This Unlock?
The real value isn't the panel itself — it's the closed-loop testing it enables. Here are concrete use cases:
1. Catching layout breakage on small screens. Ask Claude to run the app on the iPhone SE simulator, scroll through the content, and report what gets clipped. The SE's 4.7-inch screen exposes layout bugs that look fine on the default 6.1-inch simulator — and now Claude can find those bugs itself instead of you squinting at a screenshot.
2. Onboarding flow verification. "Build the app, launch it in the simulator, tap through the entire sign-up flow, and tell me if every screen renders correctly." Claude boots the app, goes screen by screen, reads each one, and flags anything that looks wrong — all before you touch a build button.
3. Visual regression checking. After Claude modifies a screen, ask it to relaunch the app and verify the change. The app relaunches in the same panel, and Claude confirms (or catches) the fix visually rather than just asserting "the code should work now."
4. Walkthrough recordings for teams. The Cmd+R screen recording saves a video of the device to your Desktop. If you're shipping a new screen, record Claude walking through it and share the clip with your team — no QuickTime or screen-capture software needed.
5. Iterative UI polish. Tell Claude the onboarding button should be bigger and the spacing between the title and subtitle should be tighter. It changes the code, rebuilds, re-launches in the same panel, and you both see the result. The feedback loop drops from minutes (build, run, check, fix) to seconds.
For broader context on where this fits in the agentic coding landscape — particularly how Claude Opus 5 and other frontier models handle multi-step agentic coding tasks — the iOS Simulator panel is a natural extension of the trend: agents that can not only write code but also observe and correct their own output.
Common Problems and How to Fix Them
The panel doesn't open when Claude runs the app
Claude likely didn't recognize you wanted the app run. State the goal explicitly: "Run the app in the iOS Simulator and tap through the signup flow" — not just "fix this bug." Also verify you're on Claude Desktop v1.24012.0+ (check under Claude > Check for Updates), and confirm Xcode and the Simulator are installed by launching the standalone Simulator app.
If your organization manages Claude Code, the simulator tools may be disabled by policy — check for the disableMobileSimulatorTools managed setting.
The panel says "no simulators were found"
Xcode is installed but has no iOS simulator runtime. The panel shows the setup steps and checks each one off as you complete it. To install the missing runtime manually, run xcodebuild -downloadPlatform iOS in your terminal, or download it from Xcode's Settings > Components.
The panel is slow or makes my Mac sluggish
Drop the video stream settings — frame rate, resolution — before blaming the tool. The default settings stream a high-quality video feed of the device, and on older Macs or machines under heavy load, that can be the bottleneck, not the feature itself. Switching encoding from H.264 to JPEG can also reduce decode load.
My Mac won't let Claude control the device
The first time Claude uses a device, the desktop app asks for one-time consent. If you declined, the device still boots and the panel works for your own taps. Click "Let Claude use it" in the panel to grant access retroactively. You do not need to grant macOS Accessibility or Screen Recording system permissions — the panel drives the device directly.
I'm on an Enterprise plan and the feature doesn't appear
The iOS Simulator panel is not available on Enterprise plans as of the public beta. Check with your Anthropic account representative for timeline updates, or use a Pro or Max plan for individual evaluation.
Who Is This For — and Who Is It Not For?
This is for:
- iOS developers who already use Claude Code and want to cut the build-run-check cycle down to seconds.
- Non-developers on iOS teams who need to see a change on a device without waiting for a full build.
- Learners building their first apps — watching the app boot, break, and get fixed teaches the shape of the work faster than reading a stack trace.
This is not for:
- Anyone who needs to test on physical hardware. Claude drives simulated devices only. To test on a real iPhone or iPad, run the app from Xcode yourself, then tell Claude what you see or attach a screenshot.
- Cloud or SSH sessions. The panel requires a local session because the simulator runs on your Mac and the Claude instance needs to reach it directly.
- Enterprise plan holders, at least for the current beta cycle.
If you're exploring the broader ecosystem of AI coding agents and agentic coding tools, the iOS Simulator panel represents a meaningful differentiator for Claude Code specifically — most competing agents (Codex, Gemini Code Assist, open-source alternatives) don't yet have equivalent native simulator integration.
What This Means for You
If you build iOS apps and you're on a Claude Pro, Max, or Team plan, the iOS Simulator panel turns the most tedious part of mobile development — the manual build-run-look-fix cycle — into something the agent can do itself. Start by updating to Claude Desktop v1.24012.0, confirm Xcode has the iOS runtime installed, and begin your next session with an explicit run instruction: "Build the app and run it in the simulator to check the onboarding flow."
The two things to keep in mind: use test accounts (screenshots go to Anthropic), and name the device if you care about layout (the iPhone SE catches what the iPhone 16 misses). Everything else, the panel handles automatically.
FAQ
Q: Is the Claude Code iOS Simulator panel free? A: It's included in Claude Pro ($20/month), Max ($100–$200/month), and Team plans ($25–$125/seat/month) at no additional cost. It is not available on the Free or Enterprise plans as of the July 2026 public beta.
Q: Does the iOS Simulator panel work on Windows or Linux? A: No. It requires a Mac because Apple's iOS Simulator runs only on macOS. The desktop app also requires Claude Desktop v1.24012.0 or later plus Xcode with the iOS platform installed.
Q: Does Claude need macOS Accessibility or Screen Recording permissions?
A: No. The desktop panel drives the simulator directly via Apple's simctl tooling, bypassing the screen-capture approach that requires those permissions. From the CLI, however, Claude reaches the simulator through computer use, which does require those permissions.
Q: Can Claude control a physical iPhone or iPad? A: No. Claude can only control simulated devices. For physical hardware testing, run the app from Xcode yourself and attach screenshots or describe what you see for Claude to work from.
Q: Are screenshots from the simulator sent to Anthropic? A: Yes. Claude's screenshots of the simulated device are transmitted to Anthropic and retained under your normal conversation retention settings. Anthropic recommends using test accounts rather than signing in to real accounts on any device Claude controls.
Q: Why doesn't the panel appear in my session? A: The four most common causes: (1) you're in a cloud or SSH session instead of a local one, (2) you're on an Enterprise plan where the feature is excluded, (3) Claude Desktop is below v1.24012.0, or (4) you phrased your request as a code fix rather than a run instruction — Claude needs to detect a "run" or "verify" intent to open the panel.
Discussion
0 comments