swift verge
Title: Windows local gateway: status/probe works, but cron/session/control RPC paths fail with gateway closed (1008): pairing required
Environment
OpenClaw version: 2026.3.28,
OS: Windows 10.0.26200 x64,
Gateway mode: local,
Bind: loopback,
Auth mode: token,
Channel: Discord enabled and working,
Observed behavior
Some OpenClaw commands work normally:
openclaw status,
openclaw gateway status,
openclaw gateway status reports:
service running,
listener on 127.0.0.1:18789,
RPC probe: ok,
But a number of other commands consistently fail with:
gateway connect failed: GatewayClientRequestError: pairing required
Error: gateway closed (1008): pairing required
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: C:\Users\donov.openclaw\openclaw.json
Bind: loopback
Commands that fail
openclaw cron status,
openclaw cron add ...,
openclaw gateway health,
openclaw gateway call health,
openclaw logs --follow,
session spawning / subagent spawn from the assistant side,
Commands that work
openclaw status,
openclaw gateway status,
openclaw pairing list reports: no pending Discord pairing requests,
openclaw doctor --fix did not resolve it,
stop/start / restart cycle did not resolve it,
config appears normal for local use:
gateway.mode = local,
gateway.bind = loopback,
gateway.auth.mode = token,
,
gateway.controlUi.allowInsecureAuth was previously true, then changed to false; issue persists either way,
Current config (relevant parts)
local loopback gateway,
token auth,
no remote gateway configured,
Question
Why would status / gateway status succeed, including RPC probe: ok, while cron, gateway health, gateway call health, logs, and session-control paths fail with pairing required on the same local gateway?
Is this a known Windows/local-token-auth issue, a control-path auth bug, or a config/state corruption problem?