argent-metro-debugger

1. Prerequisites

Physical iPhone: not supported; every debugger-* tool rejects kind: "device".

• React Native (iOS / Android): Metro running (default localhost:8081) and the app connected to it. Verify with debugger-status.
• Android: a physical device, a TV emulator, or a dev client that loads from localhost needs adb -s <serial> reverse tcp:<port> tcp:<port> (default 8081). If list-devices returns a hint about the adb server, prefix the command as the hint shows. Run it again after a reboot or an adb restart; Argent doesn't restore it. A bare RN app on a phone emulator uses 10.0.2.2 and doesn't need it; react-native run-android and expo run:android set it up themselves.
• Vega (Fire TV): a Debug .vpkg (a Release build never attaches) and Metro reachable from the device (vega device start-port-forwarding --port 8081 --forward false). debugger-component-tree, debugger-inspect-element, debugger-reload-metro and the react-profiler-* / profiler-* tools are unavailable there; see references/vega.md of the argent-tv-interact skill.
• Chromium (CDP): an Electron app booted with boot-device electronAppPath, or a Chromium browser exposing a CDP port (list-devices finds it). Pass its chromium-cdp-<port> id as device_id. Only debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry, view-network-logs and view-network-request-details work there; the other debugger and profiler tools are React Native only.

2. Tools

Pass the same device_id, the id from list-devices, to every call. With two or more devices on one Metro, debugger-connect refuses a udid or serial and returns a logicalDeviceId: use that as device_id from then on, and include it in stop-all-simulator-servers' devices at teardown, or the debugger session outlives yours.