Why did OpenClaw subagent spawning break after upgrading to 4.21?

The upgrade resets device scopes in paired.json to operator.read only, but the new version requires additional scopes for subagent and approval operations.

How do I fix the scope upgrade pending approval error?

Manually edit ~/.openclaw/devices/paired.json to add all required scopes (operator.write, operator.approvals, operator.admin, operator.pairing, operator.secrets) and set chmod 444 to prevent overwriting.

Is the scope upgrade bug in OpenClaw 4.21 fixed?

The workaround is manual. The issue suggests openclaw doctor --fix should auto-detect and fix missing scopes during upgrades.

What error message does the scope upgrade bug show?

The error is: pairing required: device is asking for more scopes than currently approved.

Does this affect all OpenClaw 4.21 upgrades?

It affects upgrades from 4.15 or earlier to 4.21 where existing device pairings had legacy scope sets.

← Back to dashboard

clawsmith.com/signal/openclaw-v2026-4-21-scope-upgrade-breaks-subagents

⚠ IssueWide OpenLive

OpenClaw v2026.4.21 upgrade resets device scopes, breaks subagent spawning

After upgrading to v2026.4.21, device scopes in paired.json reset to operator.read only. Subagent spawning and native approval operations fail with scope upgrade pending approval error.

Product Idea from this Signal

A CLI tool that aggregates community stability reports per OpenClaw version and blocks updates that other users on your platform and channel combo report as broken

OpenClaw ships a new release roughly every two days, and three consecutive updates (v2026.4.24, 4.25, 4.26) broke gateways, Discord, Telegram, and WhatsApp for thousands of users. The built-in stable channel with delay jitter still delivers broken versions because there is no feedback loop from the community. This tool collects pass/fail reports per version per platform/channel/OS combination, exposes a pre-update check via CLI, and automatically delays updates until the target version reaches a community-validated stability threshold for your exact deployment fingerprint.

CLIOPEN-SOURCERELIABILITYCOMMUNITYDEVTOOL

CompetitiveView Opportunity →