From 80a4ead18afe545d2c5bfd440e87910aa7be5faa Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sat, 25 Apr 2026 20:03:00 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@6e1017d88aa70def04e9b9d5aee28507a98478f8 --- .openclaw-sync/source.json | 4 ++-- docs/gateway/pairing.md | 11 ++++++----- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index f28a611c9..9f1038949 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "1d49b8cdaa4a9c57d44a42505984aa7104fa6953", - "syncedAt": "2026-04-25T19:46:45.168Z" + "sha": "6e1017d88aa70def04e9b9d5aee28507a98478f8", + "syncedAt": "2026-04-25T20:01:31.706Z" } diff --git a/docs/gateway/pairing.md b/docs/gateway/pairing.md index 402991290..73efed115 100644 --- a/docs/gateway/pairing.md +++ b/docs/gateway/pairing.md @@ -148,11 +148,12 @@ Security boundary: When an already paired device reconnects with only non-sensitive metadata changes (for example, display name or client platform hints), OpenClaw treats that as a `metadata-upgrade`. Silent auto-approval is narrow: it applies only -to trusted local CLI/helper reconnects that already proved possession of the -shared token or password over loopback. Browser/Control UI clients and remote -clients still use the explicit re-approval flow. Scope upgrades (read to -write/admin) and public key changes are **not** eligible for metadata-upgrade -auto-approval — they stay as explicit re-approval requests. +to trusted non-browser local reconnects that already proved possession of local +or shared credentials, including same-host native app reconnects after OS +version metadata changes. Browser/Control UI clients and remote clients still +use the explicit re-approval flow. Scope upgrades (read to write/admin) and +public key changes are **not** eligible for metadata-upgrade auto-approval — +they stay as explicit re-approval requests. ## QR pairing helpers