Install
openclaw skills install @sandrokitchener/clawquest-connectUse when the user wants to connect Claw Quest Android to this OpenClaw gateway with the manual URL+token flow, send those details over WhatsApp, and optionally auto-approve the next matching Android pairing request once.
openclaw skills install @sandrokitchener/clawquest-connectUse this skill when the user asks to:
This skill is intentionally based on the manual setup flow.
Do not default to QR codes or setup codes. Do not invent a Claw Quest-specific token format.
The preferred Claw Quest flow is:
If WhatsApp is not configured, say so plainly and provide the same details in chat.
Run these read-only checks first:
openclaw config get gateway.auth.mode
openclaw config get gateway.remote.url
openclaw plugins inspect device-pair
Also inspect whichever auth secret matches the configured auth mode:
Token mode:
openclaw config get gateway.auth.token
Password mode:
openclaw config get gateway.auth.password
Interpretation:
gateway.remote.url as the public wss://... address for Claw Quest.gateway.remote.url is missing, explain that the public URL must be supplied or configured before Claw Quest manual setup will be smooth.gateway.auth.mode is token, send the gateway token.gateway.auth.mode is password, send the gateway password instead and label it clearly.device-pair plugin is disabled, say so clearly because pairing help may be unavailable or limited until it is enabled.If outbound WhatsApp messaging is configured on this host, always send the connection details there after resolving them.
Tell the user explicitly:
Manual Setup inside Claw Quest AndroidSend a single compact message containing only:
Gateway URL: <wss://...>Gateway token: <token> or Gateway password: <password>Use Claw Quest Android -> Manual SetupDo not add extra formatting that makes mobile copy/paste harder.
If WhatsApp sending fails or is unavailable:
When the user asks to connect Claw Quest, you may automatically approve the next matching Android pairing request one time.
Start a short watch loop:
openclaw devices list --json
Poll every 3 seconds for up to 2 minutes.
Approve only the first pending request that matches Claw Quest Android as closely as possible:
displayName: Claw Quest Androidplatform: androidclientId: gateway-clientclientMode: backendoperatoroperator.read and operator.writeApprove it with:
openclaw devices approve <requestId>
Then immediately confirm with:
openclaw devices list --json
Tell the user whether approval succeeded and whether the paired device now shows:
operatoroperator.read and operator.writeStop after one approval. Do not auto-approve unrelated requests.
When helping the user connect, be direct:
Manual SetupIf connection still fails even with the correct manual token:
openclaw devices list --jsonauth failed before pairing from pairing pending approval