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

fix(control-ui): explain pairing access upgrades

Browse Source
This commit is contained in:
Ayaan Zaidi
2026-04-20 13:06:01 +05:30
parent 67d2026e22
commit 41a01cdae5
8 changed files with 231 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/web/control-ui.md
View File

@@ -58,6 +58,11 @@ If the browser retries pairing with changed auth details (role/scopes/public
key), the previous pending request is superseded and a new `requestId` is
created. Re-run `openclaw devices list` before approval.
If the browser is already paired and you change it from read access to
write/admin access, this is treated as an approval upgrade, not a silent
reconnect. OpenClaw keeps the old approval active, blocks the broader reconnect,
and asks you to approve the new scope set explicitly.
Once approved, the device is remembered and won't require re-approval unless
you revoke it with `openclaw devices revoke --device <id> --role <role>`. See
[Devices CLI](/cli/devices) for token rotation and revocation.