Skip to content

Commit 0346b15

Browse files
committed
docs: add app discovery to bootstrap flow
1 parent f7423c0 commit 0346b15

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

skills/agent-device/references/bootstrap-install.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ Open this file when you still need to choose the right target, start the right s
77
## Main commands to reach for first
88

99
- `devices`
10+
- `apps`
1011
- `ensure-simulator`
1112
- `open`
1213
- `install` or `reinstall`
@@ -21,6 +22,12 @@ Do not start acting before you have pinned the correct target and opened an `app
2122

2223
If there is no simulator, no app install, no open app session, or any uncertainty about where the app should come from, stay in this file and use deterministic setup commands or bootstrap scripts first. Do not improvise install paths or app-launch flows while exploring.
2324

25+
## If `open` fails
26+
27+
- If `open <app>` fails, or you are not sure which app name is available on the target, run `agent-device apps` first and choose from the discovered app list instead of guessing.
28+
- Use `apps --platform <platform>` together with `--device`, `--udid`, or `--serial` when target selection matters.
29+
- Once you have the correct app name, retry `open` with that exact value.
30+
2431
## Common starting points
2532

2633
These are examples, not required exact sequences. Use the smallest setup flow that matches the task.

0 commit comments

Comments
 (0)