You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: skills/agent-device/references/remote-tenancy.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Open this file for remote daemon HTTP flows that let an agent running in a Linux
15
15
-`agent-device disconnect --remote-config <path>`
16
16
-`agent-device connection status`
17
17
-`agent-device auth status`
18
-
-`AGENT_DEVICE_DAEMON_AUTH_TOKEN=...` for CI/service-token automation
18
+
-`AGENT_DEVICE_DAEMON_AUTH_TOKEN=adc_live_...` for CI/service-token automation
19
19
20
20
## Most common mistake to avoid
21
21
@@ -42,7 +42,7 @@ agent-device fill @e3 "test@example.com"
42
42
agent-device disconnect
43
43
```
44
44
45
-
After `connect`, normal commands use the active remote connection. If cloud credentials are missing, `connect` starts login automatically in an interactive shell and stores a revocable CLI session that silently mints short-lived `adc_agent_...` command tokens. The cloud side remains responsible for token expiry, tenant/run claim checks, revocation, one-time device approval, and polling rate limits. End with `disconnect` to release the lease and stop the owned Metro companion.
45
+
After `connect`, normal commands use the active remote connection. If cloud credentials are missing, `connect` starts login automatically in an interactive local shell and stores a revocable CLI session that silently mints short-lived `adc_agent_...` command tokens. Linux sandboxes, CI, and other non-interactive shells should set `AGENT_DEVICE_DAEMON_AUTH_TOKEN=adc_live_...` instead. The cloud side remains responsible for token expiry, tenant/run claim checks, revocation, one-time device approval, and polling rate limits. End with `disconnect` to release the lease and stop the owned Metro companion.
46
46
47
47
### Self-contained script flow
48
48
@@ -72,7 +72,7 @@ The first command that needs a lease or Metro runtime prepares and persists it.
72
72
## Behavior summary
73
73
74
74
-`connect` stores local non-secret connection state and defers tenant lease allocation plus Metro preparation until a later command needs them.
75
-
- Commands such as `install-from-source`, `open`, `snapshot`, and `apps` allocate or refresh the lease when needed.
75
+
- Commands such as `install-from-source`, `open`, `snapshot`, `devices`, and `apps` allocate or refresh the lease when needed.
76
76
-`open` prepares Metro runtime hints when the remote profile has Metro fields and no compatible runtime is already saved.
77
77
-`metro reload` reuses saved Metro runtime hints and asks Metro to reload connected React Native apps without restarting the native process.
78
78
-`batch` also prepares Metro when any step opens an app and that step does not provide its own runtime.
@@ -126,6 +126,7 @@ Optional overrides stay available for advanced cases:
126
126
- Put `tenant`, `runId`, and `sessionIsolation` in the remote profile so agents can run `agent-device connect --remote-config ./remote-config.json` without extra scope flags. Add `platform`, `leaseBackend`, `session`, or Metro overrides only when the default inference is not enough for that flow.
127
127
- Explicit command-line flags override connected defaults. Use them intentionally when switching session, platform, target, tenant, run, or lease scope.
128
128
- For React Native Metro runs with `metroProxyBaseUrl`, `agent-device >= 0.11.12` can manage the local companion tunnel, but Metro itself still needs to be running locally. `metroProxyBaseUrl` is the bridge origin, not a prebuilt `/api/metro/...` route.
129
+
- Set `AGENT_DEVICE_CLOUD_BASE_URL` to the bridge/control-plane API origin. It does not need to be the dashboard origin; `/api-keys` on the bridge can redirect to the dashboard for service-token setup.
129
130
- For cloud stock React Native iOS, use the bridge descriptor's wildcard HTTPS Metro hints directly; do not install or launch the XCTest runner just to make Metro reachable.
130
131
- Android keeps using bridge-provided `/api/metro/runtimes/<runtimeId>/...` Metro routes.
131
132
-`metroPublicBaseUrl` is only needed for direct/non-bridge bundle hints. Bridged profiles can omit it.
0 commit comments