Request Device pairing | Friends of the Crustacean 🦞🤝 | Page 1

proper grotto Apr 21, 2026, 11:36 PM

#

agent:main:discord:channel:1495910797333893184 (17m ago)
agent:main:discord:direct:1315374465282084915 (27m ago)
gateway connect failed: GatewayClientRequestError: scope upgrade pending approval (requestId: d6e86222-4583-4f4c-98f1-a3d5f1e37c24)
│
◇ Device pairing ───────────────────────────────────────────────────────────────────────────╮
│ │
│ - Pending scope upgrade d6e86222-4583-4f4c-98f1-a3d5f1e37c24 for │
│ gateway:device.pair.list │
│ (e0d174faa08fc39393e869ddf365d3d9b079cdd97b08c2cafd6aa9fe5ca6c77d): approved scopes │
│ [operator.read], requested scopes [operator.pairing]. Review with openclaw devices │
│ list, then approve with openclaw devices approve d6e86222-4583-4f4c-98f1-a3d5f1e37c24. │
│

trim violetBOT Apr 21, 2026, 11:37 PM

#

This is a scope-upgrade approval, not a generic auth failure.

Your device currently has only operator.read, but pairing actions need operator.pairing, so approve the pending request on the gateway host:

openclaw --version
openclaw devices list
openclaw devices approve d6e86222-4583-4f4c-98f1-a3d5f1e37c24

A couple gotchas:

run that locally on the gateway machine if you can
devices approve needs operator.pairing or operator.admin
if the device retried, the old request can get superseded, so check openclaw devices list first and approve the current exact requestId

Docs:

#

If devices approve still fails, paste:

openclaw --version
output of openclaw devices list

and I’ll help narrow it down.

proper grotto Apr 21, 2026, 11:40 PM

#

gateway connect failed: GatewayClientRequestError: scope upgrade pending approval (requestId: d9071268-d4da-4c08-9b9d-c75858ade4ee)
◇
Direct scope access failed; using local fallback.
unknown requestId

trim violetBOT Apr 21, 2026, 11:40 PM

#

Yep, that usually means the requestId already rotated and the one you approved is stale.

unknown requestId here = “that pending request no longer exists”.

Try this sequence on the gateway host:

openclaw --version
openclaw devices list
openclaw devices approve d9071268-d4da-4c08-9b9d-c75858ade4ee

But only use that ID if devices list still shows it. If not, approve the newest exact ID from the list.

What’s happening:

the client retried pairing
OpenClaw superseded the old pending entry

#

approving the old ID returns unknown requestId

If it keeps changing, do this:

trigger the connect once
immediately run openclaw devices list
approve the current pending ID right away

If it still fails, paste:

openclaw --version
openclaw devices list --json

Docs: https://docs.openclaw.ai/cli/devices

proper grotto Apr 21, 2026, 11:50 PM

#

Workspace bootstrap files are near configured limits: │
│ - AGENTS.md: 10,428 chars (87% of max/file 12,000) │
│ Total bootstrap injected chars: 13,593 (23% of max/total 60,000). │
│ Total bootstrap raw chars (before truncation): 13,593.

trim violetBOT Apr 21, 2026, 11:51 PM

#

That one is just a warning, not the cause of your pairing issue.

What it means:

AGENTS.md is at 87% of the per-file bootstrap cap
total injected bootstrap is only 23% of the total cap
so the only thing close to the limit is AGENTS.md, not the whole prompt

Default limits from docs:

agents.defaults.bootstrapMaxChars: 12000
agents.defaults.bootstrapTotalMaxChars: 60000

So right now you’re still under budget. It only becomes a real problem once OpenClaw starts truncating the file, which can cause lower sections of AGENTS.md to stop being injected.

My recommendation:

ignore it for now if nothing is being truncated
if it keeps growing, trim AGENTS.md first

#Request Device pairing