Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Code CLI 6 Nov 2026
One change · claude-code

Test iOS apps in the simulator changeddesktop-ios-simulator

Nearest release: v2.1.319, published 2 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 6 Nov 2026 03:36 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 6 Nov 2026 03:37 UTC.

Upstream edited
Recorded here
Lines+9added
Lines−3removed
From line 1 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits15to this page, all time

The whole hunk

from line 1, old and new numbered
/
lines
from line 1
11# Test iOS apps in the simulator
22 
3> Claude Code Desktop opens your app in the iOS Simulator pane when Claude builds, runs, or checks it, with a separate simulator for each session.
3> Claude Code Desktop opens your app in the iOS Simulator pane when Claude builds, runs, or checks it.
44 
55> [!NOTE]
66>
from line 84
8484 
8585## How sessions manage devices
8686 
87Each device belongs to the session that launched it, so [parallel sessions](https://code.claude.com/docs/en/desktop.md#work-in-parallel-with-sessions) don't share a device: what you see in one session's pane reflects that session's work, not another's. Switching sessions in the sidebar switches the simulator view along with the conversation, and switching back resumes the same device where it left off. If Claude works with more than one device, each opens its own pane, up to 4 per session.
87If your prompt doesn't name a simulator, Claude uses one that's already running, even if another [parallel session](https://code.claude.com/docs/en/desktop.md#work-in-parallel-with-sessions) opened it. To give each session its own simulator, name a different one in each session's prompt.
8888 
8989Claude Code Desktop shuts down the simulators it booted once they're no longer in use: when you quit the app, when you archive the session, or 10 minutes after you detach a device from its pane. Devices you boot outside Claude Code Desktop, such as in Apple's Simulator app or in Device Hub, are never shut down automatically. To shut down the attached device right away, use the shutdown button in the pane.
9090 
from line 98
9898 
9999After 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 
101If 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.
101If you decline Claude's request, the device doesn't attach and Desktop doesn't boot it. To use the device yourself:
102 
1031. Click **Attach simulator** in the pane.
1042. Click **Continue** on the permission screen.
1053. Click **Cancel** in the dialog that follows.
106 
107The device attaches and works for your own taps, and Claude's access stays off. After that, to give Claude access, click **Let Claude use it** in the pane.
102108 
103109### Actions that follow your permission mode
104110 
Feedback