@devries-cameron20 / t3code Mirror · read-only
Fork 0

The best way to control Claude Code, Codex and more from any computer or phone

Mirrored from https://github.com/Camo67/t3code.git

Synced Nov 21, 07:15 UTC

main
md 84 lines 4.14 KB
Rendered Raw
1 ---
2 name: test-t3-mobile
3 description: Test T3 Code's native iOS and Android app through its Device panel and returned AgentDevice command. Use for mobile verification, native-client builds, Metro launch, and mobile pairing against isolated development state.
4 ---
5
6 # Test T3 Mobile
7
8 ## Open the device
9
10 Call `device_list`, then `device_open` with the selected host and device IDs.
11 T3 boots the device and shows its live stream in the Device panel. Follow its
12 returned `quickStart`, using the exact `agentDevice.command` and all `targetArgs`
13 on every operation. Use `device_screenshot` to inspect the screen.
14
15 If T3 device tools or the selected device are unavailable, report the blocker
16 and stop verification. Do not install or switch to another automation system.
17
18 ## Use an isolated backend
19
20 Reuse this task's healthy backend. Otherwise run `vp run dev` from the
21 repository root, retain its terminal session, and read the actual backend port
22 from the dev-runner output. Use the worktree's ignored `.t3` state. Never run
23 against `~/.t3/userdata`. The Browser panel is not required for this workflow.
24
25 Test with meaningful project and thread data. Read the shared
26 [SQLite fixture reference](../test-t3-app/references/sqlite-fixtures.md) only
27 when inspecting or seeding SQLite. Stop the test server before fixture writes.
28
29 ## Launch T3 Code Dev
30
31 From the checkout being tested on the selected device host, run:
32
33 ```bash
34 vp run mobile:install <ios|android> <device-id>
35 ```
36
37 This installs the dev client for the checkout's native fingerprint: from the
38 device, the local cache, or the shared cache in seconds, building once only
39 when no machine has that fingerprint yet: in the `Mobile Dev Client` workflow
40 on Blacksmith when HEAD is pushed and `gh` may dispatch it (the command waits),
41 otherwise here (5-15 minutes, logged to the file it names). The device id may be omitted when exactly one device is booted. It
42 prints one JSON line; on failure it names the next command. Mobile verification
43 includes that step unless the user prohibits it.
44
45 For a device you opened in an agent-device session elsewhere (a device pool,
46 cloud, or remote host), run `vp run mobile:install <ios|android> --session <s>
47 --config <file>` from the directory you opened the session in, passing the
48 `--config` file from `device_open`'s `targetArgs`. Without it, a device pool's
49 gateway refuses the install, wrongly saying agent-device is too old. It installs
50 the cached build into that session (`--abi arm64-v8a` for an ARM Android device;
51 pool Android emulators are x86_64, the default; `--metro <url>` also opens it
52 against Metro). Without a cached build for this checkout it builds first, which can
53 outlast the lease, so run `vp run mobile:install <ios|android> --prepare` (with
54 the same `--abi`) before you open the device.
55
56 Start `vp run dev:client` from `apps/mobile`, or reuse a healthy Metro belonging
57 to this checkout. Open its printed development-client URL with AgentDevice
58 `open com.t3tools.t3code.dev <url>` and all returned target arguments.
59 The device must be able to reach both Metro and the isolated backend.
60 Append `&disableAutoLaunch=1&disableFab=1` to the development-client URL query
61 when developer chrome would obscure screenshots or taps; the SDK 58 dev client
62 applies these preferences before the app loads.
63
64 ## Pair and verify
65
66 Use the helper from the repository root, with the returned executable and target
67 arguments stored in `agent_device_command` and the Bash array
68 `agent_device_target_args`:
69
70 ```bash
71 .agents/skills/test-t3-mobile/scripts/pair-client.sh \
72 <server-port> <base-dir> <device-reachable-backend-origin> \
73 "$agent_device_command" "${agent_device_target_args[@]}"
74 ```
75
76 It issues a fresh credential and opens T3 Code Dev's existing pairing route
77 through AgentDevice. For a backend on the device host, use
78 `http://127.0.0.1:<server-port>` on iOS or `http://10.0.2.2:<server-port>`
79 on Android. For a remote backend, use its reachable origin.
80
81 Confirm the intended projects appear, exercise the affected flow, and capture
82 evidence. Retain the app and environment while iterating. At teardown, remove
83 the disposable connection, close the AgentDevice session, call `device_close`,
84 and stop only your backend and Metro processes.