openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@b2efd19648

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-05-04 07:15:08 +00:00
parent 008982029a
commit 00b64ce66f
2 changed files with 10 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "826786b114a45ca5f9b341d5216911837fc55a12",
"syncedAt": "2026-05-04T07:05:52.631Z"
"sha": "b2efd1964800ca8b57b0a74eec4ef15ec837b768",
"syncedAt": "2026-05-04T07:13:11.794Z"
}

9
docs/channels/pairing.md
View File

@ -113,7 +113,7 @@ If you use the `device-pair` plugin, you can do first-time device pairing entire
1. In Telegram, message your bot: `/pair`
2. The bot replies with two messages: an instruction message and a separate **setup code** message (easy to copy/paste in Telegram).
3. On your phone, open the OpenClaw iOS app → Settings → Gateway.
4. Paste the setup code and connect.
4. Scan the QR code or paste the setup code and connect.
5. Back in Telegram: `/pair pending` (review request IDs, role, and scopes), then approve.
The setup code is a base64-encoded JSON payload that contains:
@ -134,6 +134,13 @@ That bootstrap token carries the built-in pairing bootstrap profile:
Treat the setup code like a password while it is valid.
For Tailscale, public, or other non-loopback mobile pairing, use Tailscale
Serve/Funnel or another `wss://` Gateway URL. Direct non-loopback `ws://` setup
URLs are rejected before QR/setup-code issuance. Plaintext `ws://` setup codes
are limited to loopback URLs; private-network `ws://` clients still require the explicit
`OPENCLAW_ALLOW_INSECURE_PRIVATE_WS=1` break-glass described in the remote
Gateway guide.
### Approve a node device
```bash