Skip to content

Commit 63e28a0

Browse files
docs(devices): note why the launcher withholds device selectors
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent ad133fa commit 63e28a0

1 file changed

Lines changed: 6 additions & 1 deletion

File tree

‎docs/internals/devices.md‎

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,12 @@ device and cannot drift from the pinned CLI version. `device_open` returns a
118118
launcher bound to its agent-device session, so agents need no target flags.
119119
The launcher leaves out the flags a command refuses (`cdp` talks to Metro, not
120120
to the device), refuses the commands that would replace T3's connection, and
121-
checks that connection first: agent-device reports a sandboxed shell and a
121+
gives device selectors only to commands that choose the device or check its
122+
claim: agent-device runs any other command on a selected device without a claim
123+
check, so a session whose `open` lost to another thread could drive its device.
124+
`batch`, `replay` and `test` pass selectors to every step, so they refuse to run
125+
while another session holds the device. The launcher also checks T3's
126+
connection before each command: agent-device reports a sandboxed shell and a
122127
dropped tunnel alike as an unreachable daemon, so the launcher names which one it
123128
is. Ending a session (`device_close`, the Device panel, a shutdown) also closes
124129
its agent-device session, which quits the app that session opened and releases the CLI's claim on the device.

0 commit comments

Comments
 (0)