Test iOS apps in the simulator changeddesktop-ios-simulator
Upstream edited this page at 5 Nov 2026 08:50 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 5 Nov 2026 09:07 UTC.
Upstream edited
Recorded here
Lines+4added
Lines−3removed
From line
90
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits14to this page, all time
The whole hunk
from line 90, old and new numbered
/
from line 90
9090
9191## Grant Claude access to a device
9292
93Claude asks for your consent before it controls a device, while building the app or opening a URL on it follows your session's permission mode. You or your organization can also turn Claude's access off entirely.
93Claude asks for your consent before it controls a device, while building or launching the app or opening a URL on it follows your session's permission mode. You or your organization can also turn Claude's access off entirely.
9494
9595### Allow a device the first time
9696
9797The first time Claude uses a simulator, the desktop app asks you to allow it. The consent covers controlling that device and taking screenshots of it, and you give it once per device rather than once per session. Claude's screenshots of the device are sent to Anthropic and kept under your normal conversation retention settings, so don't sign in to real accounts on a device Claude uses.
9898
99After you allow a device, Claude's actions on it, such as tapping, typing, launching the app, and taking screenshots, run without further prompts. They carry the same trust as you clicking in the pane, and they only touch the simulated device, so the pane doesn't need the macOS Accessibility and Screen Recording permissions that computer use requires.
99After you allow a device, Claude's actions on it, such as tapping, typing, and taking screenshots, run without prompts, but you approve launching the app as your [permission mode](#actions-that-follow-your-permission-mode) requires. They carry the same trust as you clicking in the pane, and they only touch the simulated device, so the pane doesn't need the macOS Accessibility and Screen Recording permissions that computer use requires.
100100
101101If you decline, the device still boots and the pane still works for your own taps; only Claude's access stays off. To change your mind later, click **Let Claude use it** in the pane.
102102
103103### Actions that follow your permission mode
104104
105Two actions follow your session's [permission mode](https://code.claude.com/docs/en/permissions.md#permission-modes) instead of the one-time consent:
105Three actions follow your session's [permission mode](https://code.claude.com/docs/en/permissions.md#permission-modes) even after you allow a device:
106106
107107* Opening a URL on the device, for example to test a deep link or load a page in the device's Safari, because a URL can carry data off the device.
108108* Building the app, because `xcodebuild` runs your project's build scripts on your Mac. Checking on a build already in progress doesn't prompt.
109* Installing and launching the app, because Claude can run any app it names, not only the one you're building.
109110
110111### Turn off simulator access
111112
No line in this hunk matches that.