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
-`--token` and `--password` are mutually exclusive.
37
37
- The setup code itself now carries an opaque short-lived `bootstrapToken`, not the shared gateway token/password.
38
+
- Normal QR/setup-code mobile onboarding is one step: scan the QR or paste the setup code, then the app connects with bootstrap auth and the Gateway silently approves the fresh baseline mobile device plus its node pairing.
39
+
-`openclaw qr` also prints an 8-character setup short code. The short code is a 5-minute, single-use pointer to the same setup-code payload on that Gateway. A bare short code still needs the app to know which Gateway host to redeem against; the QR/setup code carries the Gateway URL directly.
38
40
- Built-in setup-code bootstrap returns a primary `node` token with `scopes: []` plus a bounded `operator` handoff token for trusted mobile onboarding.
39
41
- The handed-off operator token is limited to `operator.approvals`, `operator.read`, `operator.talk.secrets`, and `operator.write`; `operator.admin` and `operator.pairing` require a separate approved operator pairing or token flow.
42
+
- Auto-approval is limited to the fresh setup-code mobile baseline. Later role, scope, metadata, or node capability upgrades still create pending requests that require explicit approval.
40
43
- Mobile pairing fails closed for Tailscale/public `ws://` gateway URLs. Private LAN addresses and `.local` Bonjour hosts remain supported over `ws://`, but Tailscale/public mobile routes should use Tailscale Serve/Funnel or a `wss://` gateway URL.
41
44
- With `--remote`, OpenClaw requires either `gateway.remote.url` or
42
45
`gateway.tailscale.mode=serve|funnel`.
@@ -46,9 +49,10 @@ openclaw qr --url wss://gateway.example/ws
46
49
-`gateway.auth.password` resolves when password auth can win (explicit `gateway.auth.mode="password"` or inferred mode with no winning token from auth/env).
47
50
- If both `gateway.auth.token` and `gateway.auth.password` are configured (including SecretRefs) and `gateway.auth.mode` is unset, setup-code resolution fails until mode is set explicitly.
48
51
- Gateway version skew note: this command path requires a gateway that supports `secrets.resolve`; older gateways return an unknown-method error.
49
-
-After scanning, approve device pairing with:
52
+
-If onboarding reports a pending repair or upgrade instead of connecting, review it with:
50
53
-`openclaw devices list`
51
-
-`openclaw devices approve <requestId>`
54
+
-`openclaw nodes pending`
55
+
-`openclaw devices approve <requestId>` or `openclaw nodes approve <requestId>`
0 commit comments