Gateway connection blocked: missing scope operator.read

[huhaiting]

Problem Description

After connecting to the OpenClaw gateway, the Control Center shows 'Gateway blocked' status. The gateway logs show:

⇄ res ✗ status 0ms errorCode=INVALID_REQUEST errorMessage=missing scope: operator.read ⇄ res ✗ system-presence 1ms errorCode=INVALID_REQUEST errorMessage=missing scope: operator.read ⇄ res ✗ config.get 0ms errorCode=INVALID_REQUEST errorMessage=missing scope: operator.read

Environment

• OpenClaw version: 2026.3.13
• Control Center version: 0.1.1
• Gateway: ws://127.0.0.1:18789
• Platform: Windows

What I've tried

1. Restarted the gateway - error persists
2. Manually added operator.read to the device scopes in paired.json - error persists
3. Checked paired.json - the Control UI device has scopes: operator.admin, operator.approvals, operator.pairing (but operator.read is missing)

Screenshot

Questions

1. Is there a way to properly grant operator.read scope to the Control Center device?
2. Is this a known issue with the 2026.3.13 gateway version?
3. Should the Control Center request operator.read during connection setup?

[TianyiDataScience]

谢谢这份日志。missing scope: operator.read 看起来更像是 Gateway 侧配对设备的 scope/能力契约问题，而不是控制中心单独某个页面的渲染问题。

我这边现在还不能安全地直接改代码，因为仓库里没有看到一个明确的 Gateway scope 配对契约可以验证“应该由控制中心请求 operator.read”还是“应该由 Gateway 在重新配对时授予”。下一步建议先用最新 OpenClaw / Control Center 重新配对一次；如果还会复现，请补充：最新版本号、重新配对后的 paired 设备 scopes、以及 Gateway 启动/配对日志里和这个设备相关的部分。