#Setup OpenClaw
1 messages · Page 1 of 1 (latest)
Oof, that’s a miserable setup loop. The good news: missing scope: operator.read usually means the gateway is reachable, but the browser/CLI token you’re using is under-scoped or stale.
First, please paste:
openclaw --version
openclaw status --all
openclaw devices list
Likely fix from the gateway machine:
openclaw devices list
openclaw devices approve --latest # preview only
openclaw devices approve <requestId>
Then reopen with a fresh dashboard link:
openclaw dashboard
If there’s no pending request, but you see a paired browser/device that looks stale, rotate its operator token:
openclaw devices rotate --device <deviceId> --role operator
Don’t run broad clears/resets yet — this is probably just device auth scope drift.
Docs: https://docs.openclaw.ai/cli/devices and https://docs.openclaw.ai/web/dashboard#if-you-see-unauthorized-1008
Hey Rapha, that missing scope: operator.read error usually means your token is stale. Try running openclaw devices list then openclaw devices approve --latest and reopen with openclaw dashboard. That should fix it.
If you need help let me know.