vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 15:30:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: allow native app metadata reconnects

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-25 21:00:25 +01:00
parent 89c52988c5
commit 6e1017d88a
5 changed files with 87 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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