mirror of
https://github.com/openclaw/openclaw.git
synced 2026-03-12 07:20:45 +00:00
2.1 KiB
2.1 KiB
summary, read_when, title
| summary | read_when | title | ||
|---|---|---|---|---|
| CLI reference for `openclaw qr` (generate iOS pairing QR + setup code) |
|
qr |
openclaw qr
Generate an iOS pairing QR and setup code from your current Gateway configuration.
Usage
openclaw qr
openclaw qr --setup-code-only
openclaw qr --json
openclaw qr --remote
openclaw qr --url wss://gateway.example/ws --token '<token>'
Options
--remote: usegateway.remote.urlplus remote token/password from config--url <url>: override gateway URL used in payload--public-url <url>: override public URL used in payload--token <token>: override gateway token for payload--password <password>: override gateway password for payload--setup-code-only: print only setup code--no-ascii: skip ASCII QR rendering--json: emit JSON (setupCode,gatewayUrl,auth,urlSource)
Notes
--tokenand--passwordare mutually exclusive.- With
--remote, if effectively active remote credentials are configured as SecretRefs and you do not pass--tokenor--password, the command resolves them from the active gateway snapshot. If gateway is unavailable, the command fails fast. - Without
--remote, local gateway auth SecretRefs are resolved when no CLI auth override is passed:gateway.auth.tokenresolves when token auth can win (explicitgateway.auth.mode="token"or inferred mode where no password source wins).gateway.auth.passwordresolves when password auth can win (explicitgateway.auth.mode="password"or inferred mode with no winning token from auth/env).
- If both
gateway.auth.tokenandgateway.auth.passwordare configured (including SecretRefs) andgateway.auth.modeis unset, setup-code resolution fails until mode is set explicitly. - Gateway version skew note: this command path requires a gateway that supports
secrets.resolve; older gateways return an unknown-method error. - After scanning, approve device pairing with:
openclaw devices listopenclaw devices approve <requestId>