Skip to content
| Marketplace
Sign in
Visual Studio Code>Visualization>Device ControlNew to Visual Studio Code? Get it now.
Device Control

Device Control

Mohamed Salah Nassar

| (0) | Free
Control local iOS simulators and Android emulators in VS Code, with live views and MCP tools for Copilot and Claude Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Device Control

View and control a local iOS simulator or Android emulator from the Device Control activity view in VS Code. The view follows the device your agent targets, opens when the agent starts using it, and shows the current action and its result.

Device Control showing iPhone Duo in Book pose with the hinge at 90 degrees

Device Control showing a live Android 35 emulator and its device toolbar

Set up a device

This release runs on Apple silicon Macs.

  • iOS needs macOS, Xcode and an installed Simulator runtime. iPhone Duo needs the matching Duo runtime. Xcode 27.2 was used for development.
  • Android needs the Android SDK, platform tools, Emulator and an AVD. Set ANDROID_HOME or ANDROID_SDK_ROOT if the SDK is outside the standard location. Open VS Code with those variables available to its extension host.

Open Device Control in the Activity Bar, select a device and boot it. Select Device Control › Ios Engine in VS Code settings to switch between Built-in and simulator-use. Android always uses the built-in engine. iPhone Duo uses the simulator-use active-display engine with either setting.

Use an agent

Copilot discovers the Device Control MCP definition in VS Code. Enable its tools in your agent session. #deviceControlDevice, #deviceControlScreenshot, and #deviceControlUiTree attach context from the current device.

Claude Code uses a local stdio bridge. Install the Claude Code VS Code extension and CLI, then run Device Control: Connect Claude Code to This Window in a trusted local folder. Open a new Claude Code chat after connecting or switching engines. The command adds a machine-local MCP entry for the selected folder. It keeps the workspace's shared files and Claude's tool approval settings intact. For a CLI outside PATH, set deviceControl.claudeCommand.

Example requests for simulator-use:

  • “Select and boot my iPhone simulator. Open Settings and tell me which options are visible.”
  • “On the selected iPhone Duo, switch to Book and verify that the demo is visible on the inner display.”
  • “Inspect the sign-in screen, fill in the test credentials, and verify the resulting status.”

The opt-in engine offers compact accessibility reads, grouped actions, app lifecycle, builds, tests, logs, and recording through the local simulator-use tools. The built-in engine offers Mobile Canvas's broader device inventory and operations. The opt-in catalog includes Android input and inspection, plus shared device lifecycle. Use Built-in for specialized Android tools beyond that catalog. Agent tool lists are refreshed by a new Claude Code chat.

The iPhone Duo toolbar has Closed, Book, Open, rotation in both directions, and a 0–180° hinge slider. Drag the slider to preview the fold and release it to apply the angle. The live display bends around a vertical hinge in Book. The GPU maps each decoded frame across both halves in one draw, with a direct-to-panel Canvas fallback when WebGL is unavailable. The simulator-use live view uses a separate hardware-encoded H.264 stream. If video is unavailable, the view falls back to JPEG.

Agents can use iphone_duo_pose for presets, iphone_duo_rotate for either direction, and iphone_duo_hinge to read or set a custom angle.

The gear beside the device picker opens the iOS engine, frame rate, resolution and appearance settings from the view.

Build

From the repository root, with Node 24:

npm ci --prefix vscode --registry=https://registry.npmjs.org
npm test --prefix vscode
npm run package --prefix vscode

The package command targets Apple silicon Mac. The asset preparation script selects and checks SHA-256 for the Mobile Canvas runtime available for the build host. The opt-in engine is pinned to simulator-use 0.18.1. Release artifacts carry both projects' licenses and simulator-use's third-party notices.

Device Control is based on Mobile Canvas by Jonathan Dick. Mobile Canvas and its adapted idb portions are distributed under the notices in LICENSE. Simulator-use and the third-party components it ships have their own notices in the bundled package.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft