Summary

After WSL2 restart (wsl --shutdown), Dashboard/Webchat shows "Error: missing scope: operator.read". Auto-paired webchat devices only receive operator.admin/approvals/pairing scopes, missing operator.read and operator.write.

Steps to reproduce

1. Configure gateway with token auth, bind: lan
2. Open Dashboard in browser — device auto-pairs, everything works
3. Run wsl --shutdown from PowerShell, then restart WSL2
4. Run openclaw gateway start or systemctl --user start openclaw-gateway.service
5. Open Dashboard again (even in incognito mode)
6. Result: "Error: missing scope: operator.read" on all pages

Expected behavior

Auto-paired webchat devices should include operator.read and operator.write scopes.

Actual behavior

Auto-paired devices only get 3 scopes: operator.admin, operator.approvals, operator.pairing. Dashboard is completely non-functional. Gateway logs show continuous errors:

[ws] ⇄ res ✗ chat.history 0ms errorCode=INVALID_REQUEST errorMessage=missing scope: operator.read
[ws] ⇄ res ✗ sessions.list 0ms errorCode=INVALID_REQUEST errorMessage=missing scope: operator.read

OpenClaw version

OpenClaw 2026.2.14 (c1feda1), Ubuntu 24.04 on WSL2

Operating system

windows11/ WSL/ubuntu

Install method

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

Workaround（解法）：
Manually edit ~/.openclaw/devices/paired.json — add "operator.read" and "operator.write" to both device.scopes[] and device.tokens.operator.scopes[] for each webchat device, then restart gateway.