Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Bug: Scope upgrade pending approval error after upgrade to 2026.4.21 [1 comments, 2 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#70687•Fetched 2026-04-24 05:54:42
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
1
Author
superzmenai01superzmenai01
Participants
helderbarbozahelderbarbozasuperzmenai01superzmenai01
Timeline (top)
commented ×1

After upgrading OpenClaw from 2026.4.15 to 2026.4.21, spawn subagent and native approval operations fail with "scope upgrade pending approval" error.

Error Message

{"subsystem":"telegram/native-approvals"} connect error: scope upgrade pending approval {"subsystem":"gateway/channels/telegram"} failed to start native approval handler

Root Cause

Device scopes in paired.json were reset to only ['operator.read'] after upgrade, but new version requires additional scopes:

  • operator.approvals
  • operator.admin
  • operator.read
  • operator.write
  • operator.pairing
  • operator.talk.secrets

Fix Action

Workaround

Manually editing ~/.openclaw/devices/paired.json to add all required scopes to the affected device entry, then setting file to readonly (chmod 444) to prevent Gateway from overwriting.

Code Example

Gateway closed (1008): pairing required: device is asking for more scopes than currently approved

---

{"subsystem":"telegram/native-approvals"} connect error: scope upgrade pending approval
{"subsystem":"gateway/channels/telegram"} failed to start native approval handler
RAW_BUFFERClick to expand / collapse

Bug Report: Scope Upgrade Pending Approval Error After Upgrade to 2026.4.21

Summary

After upgrading OpenClaw from 2026.4.15 to 2026.4.21, spawn subagent and native approval operations fail with "scope upgrade pending approval" error.

Environment

  • OpenClaw Version: 2026.4.21
  • Node Version: v25.9.0
  • Platform: macOS (Darwin)
  • Deployment: Homebrew installation
  • Gateway Port: 18789

Problem Description

After performing openclaw update on April 23, 2026 at 09:50 (HKT), the following operations began failing:

  1. Spawning subagents via sessions_spawn
  2. Native Telegram approval handler

Error message:

Gateway closed (1008): pairing required: device is asking for more scopes than currently approved

Log entries show:

{"subsystem":"telegram/native-approvals"} connect error: scope upgrade pending approval
{"subsystem":"gateway/channels/telegram"} failed to start native approval handler

Timeline

  • 09:50 - OpenClaw upgraded 2026.4.15 → 2026.4.21
  • 09:52 - First scope upgrade error logged (2 minutes after upgrade)
  • Scope errors continue on every spawn attempt

Root Cause

Device scopes in paired.json were reset to only ['operator.read'] after upgrade, but new version requires additional scopes:

  • operator.approvals
  • operator.admin
  • operator.read
  • operator.write
  • operator.pairing
  • operator.talk.secrets

Workaround

Manually editing ~/.openclaw/devices/paired.json to add all required scopes to the affected device entry, then setting file to readonly (chmod 444) to prevent Gateway from overwriting.

Expected Behavior

  1. Device scopes should persist across version upgrades
  2. Or user should be prompted to approve new scopes before operations fail

Additional Context

  • This is a fresh install/upgrade scenario, not a fresh setup
  • Previously working normally on 2026.4.15
  • Error occurs on all spawn operations, not just Telegram

Reproduction Steps

  1. Have OpenClaw 2026.4.15 or earlier running normally
  2. Perform openclaw update to upgrade to 2026.4.21
  3. Attempt to spawn a subagent
  4. Observe "scope upgrade pending approval" error

extent analysis

TL;DR

Manually editing the paired.json file to include all required scopes and setting it to readonly may resolve the "scope upgrade pending approval" error.

Guidance

  • Verify that the paired.json file has been reset to only ['operator.read'] after the upgrade by checking the file contents at ~/.openclaw/devices/paired.json.
  • Add the required scopes (operator.approvals, operator.admin, operator.read, operator.write, operator.pairing, operator.talk.secrets) to the affected device entry in paired.json.
  • Set the paired.json file to readonly using chmod 444 to prevent the Gateway from overwriting the changes.
  • Attempt to spawn a subagent again to verify if the error is resolved.

Example

No code snippet is necessary for this issue, as it involves manual file editing.

Notes

This workaround assumes that the issue is caused by the device scopes being reset after the upgrade. If the issue persists after applying the workaround, further investigation may be necessary.

Recommendation

Apply the workaround by manually editing the paired.json file and setting it to readonly, as this is the most straightforward way to resolve the error in the short term.

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…
#installation#GPU compatibility#latency issue#model loading#dependency error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING