Claude Code on desktop now embeds the iOS simulator directly in a panel beside the conversation window. Build and run your app, and Claude works alongside you in real time. Available in public beta today.
During an iOS simulator session, Claude can observe the running app, interact with it, and iterate autonomously. Users can also tap through the simulator themselves at any point. Requires macOS and Xcode.
In response to a question about Android emulator support, a team member confirmed it is coming soon, following the iOS simulator launch.
A user wanted to enable '/remote-control' globally without typing it each time. The setting lives in '/config' under 'Enable Remote Control for all sessions'.
A user reported that Claude Code frequently spawns dozens of subagents even for simple, non-coding tasks. Dynamic workflow size can be adjusted or disabled entirely in '/config', and setting 'disallowedTools: Agent' in a subagent's frontmatter prevents it from spawning its own child agents.
A user asked for subagents to spawn with isolated sessions and return only short summaries to keep the main agent's context lean. Subagents already run in fresh contexts, and only their final message is returned to the main agent; the team is asking for specifics if users are still seeing context blowup.
A user requested a command to hand off prompts from the main agent into a fresh context. The response floats '/subtask' as a possible name, with a screenshot suggesting it may already be in consideration.
A user asked about accessing projects from their phone without being at their desktop. The '/remote-control' command keeps a session running on the local machine while allowing you to continue it from the Claude mobile app or web.
A user wanted to start a session in the terminal and continue it in the Claude Code desktop app. The '/desktop' command does exactly that, transferring the active session over.
A user jokingly requested a time-travel feature. The best available option is '/rewind', which rolls back session state.
The advisor tool pattern lets you escalate architectural decisions to Opus before acting. In this example, Opus correctly identified that rewriting an I/O-bound CRUD API mid-feature in Rust was a bad idea, and flatly rejected 'cool kids are doing it' as justification.
