wednesdayai qr
Generate an iOS pairing QR and setup code from your current Gateway configuration.
Usage
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--client <id>: issue the bootstrap token for a specific gateway client id, storing that client’s bounded profile. Known ids:openclaw-even-g2-node,openclaw-mentra-node(MentraOS glasses miniapp),openclaw-user-client,wednesdayai-glass-node(WednesdayAI Glass). Omitted keeps the broad setup profile. The client redeems the code on first connect and is paired silently; nodevices approvestep is needed.--identity <key>: link the bootstrap-paired device to thissession.identityLinksidentity on first connect. The key must already exist (Unknown identity "<key>". Known identities: …otherwise). With--client openclaw-user-client,--identityis required as soon as at least one identity exists:--identity <name> is required with --client openclaw-user-client once identities exist. Run "wednesdayai identity list" to see them.Applies only to the bootstrap setup code, so it cannot be combined with--legacy,--remote,--token, or--password. The stored-case key is recorded in the token and linked automatically when the device first connects, so nodevices linkstep is needed. If the identity no longer exists at that point, the device still connects but is left unlinked. If the device is already linked to a different person, the connect is refused withbootstrap_device_owned: log out, ordevices removeit, then pair again with a new setup code.wednesdayai identity link <name> --qris a shortcut for this combination. See Identities and devices.--setup-code-only: print only setup code--no-ascii: skip ASCII QR rendering--json: emit JSON (setupCode,gatewayUrl,auth,clientId,identity,urlSource)
Notes
--tokenand--passwordare mutually exclusive.--clientapplies only to the bootstrap setup code, so it cannot be combined with--legacy,--remote,--token, or--password. An unknown or profile-less client id exits non-zero. The id is normalized before it is matched: surrounding whitespace is trimmed and the value is lowercased, so--client OpenClaw-User-Clientselects the same bounded profile as the canonical lowercase id.--client openclaw-user-clientstores a bounded profile (operator role,operator.sessions.read+operator.sessions.write). Redemption binds the stored profile to the connecting client exactly: a token issued for one client id cannot be redeemed by another.--client openclaw-mentra-nodestores a bounded operator-only profile (roleoperator,operator.read+operator.write). Tokens minted from it cover chat, session reads,agents.listand voice wake get/set on the broad operator read/write surface, but never the node role or the admin, approvals, pairing or talk-secret scopes. This code pairs the MentraOS glasses miniapp.--client wednesdayai-glass-nodestores a bounded profile with rolesnode+operatorandoperator.read,operator.writeandoperator.approvalsscopes; approvals cover only exec approvals for the person the device is linked to, and tokens minted from it never carry the admin, pairing or talk-secret scopes. This code pairs WednesdayAI Glass.- When the resolved gateway URL is not loopback, the command prints one reminder naming the origin allowlist that governs the selected client:
gateway.webClient.allowedOriginsfor--client openclaw-user-client, andgateway.controlUi.allowedOriginsfor every other client. The Control UI allowlist never admits the web client, so the two are not interchangeable. - 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, localgateway.auth.passwordSecretRefs are resolved when password auth can win (explicitgateway.auth.mode="password"or inferred password mode with no winning token from auth/env), and no CLI auth override is passed. - Gateway version skew note: this command path requires a gateway that supports
secrets.resolve; older gateways return an unknown-method error. - Bootstrap setup codes approve pairing silently: the first connect redeems the setup code, so no
devices approvestep is needed; usewednesdayai devices listto confirm the device. Legacy and shared-credential forms (--legacy,--remote,--token,--password) can requirewednesdayai devices listfollowed bywednesdayai devices approve <requestId>. - The bootstrap token is issued through the gateway RPC
device.bootstrap.issue(operator.admin) when a gateway owns storage. When no gateway runs,qropens the session database locally and issues the token in-process.