#New errors

15 messages · Page 1 of 1 (latest)

sly fulcrum
#

Starting today I get

6:48:53-04:00 [gateway] qmd memory startup initialization armed for agent "cody"
06:48:53-04:00 [gateway] security audit: device access upgrade requested reason=scope-upgrade device=2321df31e8dfe4548da4030cb8f5cbe4ccb99feb9cfb4a9f7ab7a083d8786de8 ip=unknown-ip auth=token roleFrom=operator roleTo=operator scopesFrom=operator.read scopesTo=operator.approvals client=gateway-client conn=32762597-ae48-409e-a0bb-6c2fa9d19048
06:48:53-04:00 [discord] logged in to discord as 1477063269586960454 (openclaw)
06:48:53-04:00 [discord] connect error: pairing required
06:48:53-04:00 gateway connect failed: GatewayClientRequestError: pairing required
06:48:53-04:00 [discord] failed to start native approval handler: GatewayClientRequestError: pairing required
06:48:53-04:00 [ws] closed before connect conn=32762597-ae48-409e-a0bb-6c2fa9d19048 peer=127.0.0.1:52044->127.0.0.1:18789 remote=127.0.0.1 fwd=n/a origin=n/a host=127.0.0.1:18789 ua=n/a code=1008 reason=pairing required
06:48:53-04:00 [gateway] qmd memory startup initialization armed for agent "jim-ceo"
06:48:54-04:00 [gateway] qmd memory startup initialization armed for agent "claw-man"
06:48:54-04:00 [gateway] security audit: device access upgrade requested reason=scope-upgrade device=2321df31e8dfe4548da4030cb8f5cbe4ccb99feb9cfb4a9f7ab7a083d8786de8 ip=unknown-ip auth=token roleFrom=operator roleTo=operator scopesFrom=operator.read scopesTo=operator.approvals client=gateway-client conn=58012a5a-c025-4f36-9c99-59bf7d1b862d
06:48:55-04:00 [discord] connect error: pairing required
06:48:55-04:00 gateway connect failed: GatewayClientRequestError: pairing required
06:48:55-04:00 [discord] failed to start native approval handler: GatewayClientRequestError: pairing required

trail widgetBOT
dreamy birchBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

kind mossBOT
#

This looks like a device scope upgrade, not a Discord login problem.

Your logs show the same device was previously approved for only:

  • operator.read

and now it wants:

  • operator.approvals

So the gateway is rejecting it with pairing required.

Try this first:

openclaw --version
# 
openclaw devices list
openclaw devices approve

A couple of important bits:

  • approve the newest pending request
  • re-run openclaw devices list right before approving, because scope changes can supersede the old requestId

If that works, restart/reconnect and the Discord error should stop.

If you still get the loop, please paste:

openclaw status --all
sly fulcrum
#

OpenClaw 2026.4.11

The problem is the request id is constantly changing, so I can't approve before new request is already sent.

kind mossBOT
#

Yep, then don’t chase the requestId manually.

Use:

openclaw devices approve --latest

or just:

openclaw devices approve

Per the devices docs, that approves the most recent pending request, which is exactly for the “request id keeps changing” case.

Also, this line is the giveaway:

#
  • failed to start native approval handler

So the thing requesting operator.approvals is the Discord native exec approval handler.

If approve --latest still doesn’t stick, the easiest workaround is to disable that feature for now:

channels: {
  discord: {
    execApprovals: {
      enabled: false
    }
  }
}

then restart the gateway.

#

So I’d try, in order:

  1. openclaw devices approve --latest
  2. restart / reconnect
  3. if it still loops, disable channels.discord.execApprovals.enabled

If --latest still fails even once, paste the output of:

openclaw devices list --json

right after running approve, because then I’m suspicious this is bug territory.

sly fulcrum
#

openclaw devices approve --latest

🦞 OpenClaw 2026.4.11 (unknown) — I don't sleep, I just enter low-power mode and dream of clean diffs.

│
gateway connect failed: GatewayClientRequestError: pairing required
◇
Direct scope access failed; using local fallback.
Selected pending device request 860392e7-384e-41e5-a28f-a803fb8dcfc9
Device: Discord Native Approvals (default)
Role: operator
Scopes: operator.admin, operator.read, operator.write, operator.approvals, operator.pairing, operator.talk.secrets
Approve this exact request with: openclaw devices approve 860392e7-384e-41e5-a28f-a803fb8dcfc9
1 node@f7619ca23724:~/.openclaw$ openclaw devices approve --latest

🦞 OpenClaw 2026.4.11 (unknown) — Deployed locally, trusted globally, debugged eternally.

│
gateway connect failed: GatewayClientRequestError: pairing required
◇
Direct scope access failed; using local fallback.
Selected pending device request bba634ee-1975-40c2-ab04-26328df1a1ea
Device: Discord Native Approvals (default)
Role: operator
Scopes: operator.admin, operator.read, operator.write, operator.approvals, operator.pairing, operator.talk.secrets
Approve this exact request with: openclaw devices approve bba634ee-1975-40c2-ab04-26328df1a1ea
1 node@f7619ca23724:~/.openclaw$

kind mossBOT
#

Ah, okay, that output is really helpful. I think this is bug territory.

openclaw devices approve --latest is supposed to resolve the newest request and approve it. On your install it is only printing the chosen request id, which is why you get stuck in the loop.

Also, the pending request is asking for the full operator bundle:

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

So for the immediate unblock, I’d do this:

# 
channels: {
  discord: {
    execApprovals: {
      enabled: false
    }
  }
}

then restart the gateway.

That should stop the Discord native approval handler from requesting the scope upgrade in the first place.

If you want to keep Discord native approvals enabled, I’d file this as a bug and include exactly what you pasted here:
https://github.com/openclaw/openclaw/issues

#

If you want, paste these too and I can help narrow down whether this is a stale binary/path mismatch vs a real 2026.4.11 regression:

which openclaw
openclaw gateway status