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@6e1017d88a

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-25 20:03:00 +00:00
parent 7a5ca32f00
commit 80a4ead18a
2 changed files with 8 additions and 7 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": "1d49b8cdaa4a9c57d44a42505984aa7104fa6953",
"syncedAt": "2026-04-25T19:46:45.168Z"
"sha": "6e1017d88aa70def04e9b9d5aee28507a98478f8",
"syncedAt": "2026-04-25T20:01:31.706Z"
}

11
docs/gateway/pairing.md
View File

@ -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