Xcode Device Hub Workflow

Purpose

Use Device Hub as Xcode's native surface for simulated and physical device work. It owns device selection, interaction, environment inspection, pairing, captures, and diagnostics; it does not replace project build/run, test, debugger, provisioning, or browser-mirror ownership. Use xcrun devicectl as its scriptable companion only for a bounded device-management or diagnostic need, never as a substitute for an XCUITest result.

When To Use

• Use this workflow for a Device Hub request, a run-destination decision, simulator or physical-device inspection, screenshots, videos, environment variants, pairing, or downloaded diagnostics.
• Use it when a running Xcode app should be observed or interacted with through Device Hub rather than by opening a separate Simulator window.
• Hand project build, install, launch, and scheme selection to xcode-build-run-workflow.
• Hand test design and execution to xcode-testing-workflow; hand breakpoints and stack inspection to xcode-debugger-mcp-workflow.
• Hand a future local browser mirror or Swift Package preview host to the future AgentDeck runtime; do not substitute a browser bridge for Device Hub until that runtime exists and reports ready.

Workflow