Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: CLI/operator RPC stays scope-empty on local auto-approved pairing (2026.3.13) [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#51495•Fetched 2026-04-08 01:10:25
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
0
Author
AhmedKazlakAhmedKazlak
Participants
AhmedKazlakAhmedKazlakblastmannblastmannHollychou924Hollychou924
Timeline (top)
commented ×2labeled ×2

Environment:

  • OpenClaw 2026.3.13
  • macOS 26.1 arm64
  • Gateway bind=loopback, token auth enabled
  • Local CLI on same host

Evidence:

  • gateway status shows runtime running / RPC probe ok
  • channels show Telegram and Discord OK
  • gateway logs show local auto-approval followed by repeated WS missing scope: operator.read

Root Cause

Environment:

  • OpenClaw 2026.3.13
  • macOS 26.1 arm64
  • Gateway bind=loopback, token auth enabled
  • Local CLI on same host

Evidence:

  • gateway status shows runtime running / RPC probe ok
  • channels show Telegram and Discord OK
  • gateway logs show local auto-approval followed by repeated WS missing scope: operator.read
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

Environment:

  • OpenClaw 2026.3.13
  • macOS 26.1 arm64
  • Gateway bind=loopback, token auth enabled
  • Local CLI on same host

Evidence:

  • gateway status shows runtime running / RPC probe ok
  • channels show Telegram and Discord OK
  • gateway logs show local auto-approval followed by repeated WS missing scope: operator.read

Steps to reproduce

  1. Start gateway on localhost with token auth.
  2. Confirm gateway status is running and channels are OK.
  3. Clear paired devices.
  4. Run openclaw gateway probe or openclaw status --all.
  5. Gateway auto-approves local device pairing.
  6. Subsequent WS RPC calls (status, system-presence, config.get) fail with missing scope: operator.read.

Expected behavior

Local auto-approved pairing should issue/persist an operator device token with requested scopes, so operator RPC works.

Actual behavior

Connection succeeds, pairing auto-approves, but follow-up RPC remains scope-limited and probe/status report missing scope: operator.read.

OpenClaw version

2026.3.13

Operating system

macOS 26.1 arm64

Install method

No response

Model

openai/gpt-5.4

Provider / routing chain

openclaw > openAI auth

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue of missing scope operator.read after local auto-approval of device pairing, we need to ensure that the operator device token is issued with the requested scopes. Here are the steps:

  • Update the openclaw configuration to include the operator.read scope in the auto-approval settings.
  • Modify the openclaw gateway to persist the operator device token with the requested scopes.

Example code snippet to update the configuration:

import openclaw

# Update the configuration to include the operator.read scope
config = openclaw.Config()
config.auto_approval_scopes = ["operator.read"]
openclaw.save_config(config)

Example code snippet to modify the gateway:

import openclaw.gateway

# Modify the gateway to persist the operator device token with the requested scopes
class CustomGateway(openclaw.gateway.Gateway):
    def auto_approve_device(self, device):
        # Issue the operator device token with the requested scopes
        token = openclaw.gateway.issue_token(device, scopes=["operator.read"])
        return token

# Use the custom gateway
gateway = CustomGateway()

Verification

To verify that the fix worked, run the following steps:

  • Clear paired devices and restart the gateway.
  • Run openclaw gateway probe or openclaw status --all to trigger the auto-approval of local device pairing.
  • Check the gateway logs to ensure that the missing scope: operator.read error is no longer present.
  • Run subsequent WS RPC calls (status, system-presence, config.get) to verify that they succeed without scope limitations.

Extra Tips

  • Ensure that the openclaw version is up-to-date, as newer versions may include fixes for similar issues.
  • Review the openclaw documentation for any specific configuration or setup requirements for operator device tokens and scopes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Local auto-approved pairing should issue/persist an operator device token with requested scopes, so operator RPC works.

#api#ssr#installation#tensor shape#autograd error#inference speed#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING