Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Environment

• OpenClaw: v2026.4.1 (upgraded from v2026.3.12)
• OS: Windows 11 Home (Build 26200) x64
• Node: v25.8.0
• Discord: 1 guild, 9 channels, groupPolicy: allowlist

Description

After upgrading to v2026.4.1, the Discord provider fails to fully connect on the first startup attempt. It resolves channels but never reaches the "logged in" state. The health-monitor detects it as "disconnected" after ~5-7 minutes and restarts the provider. The second attempt succeeds (with "Carbon reconcile path" for native commands).

This did not occur on v2026.3.12.

Startup Log Timeline

Steps to reproduce

1. Upgrade OpenClaw from v2026.3.12 to v2026.4.1 on Windows 11.
2. Start gateway via Task Scheduler or openclaw gateway start.
3. Observe Discord provider: channels resolve but "logged in" never appears.
4. Wait ~7 minutes for health-monitor to restart the provider.
5. Second attempt succeeds with "Carbon reconcile path" log line.

Expected behavior

Expected Behavior

Discord provider should connect and reach "logged in" on the first startup attempt without requiring a health-monitor restart cycle.

Workaround

• Wait ~7 min for health-monitor to auto-restart, OR
• Ctrl+C and restart gateway manually

Additional Context

• Task Scheduler runs gateway.cmd on logon
• The terminal appears to hang after "starting provider" line (no new stdout until health-monitor kicks in)
• Config: streaming: "off", commands.native: "auto"

Actual behavior

Discord provider resolves channels on first startup but never reaches "logged in" state. Terminal output appears to hang after "starting provider (@GYOZEN-AI)" line with no new output for ~7 minutes.

After health-monitor detects "disconnected" and restarts the provider, the second attempt succeeds — logging "native commands using Carbon reconcile path" followed by "logged in" and "awaiting gateway readiness".

Gateway log evidence (timestamps in UTC+7):

• 23:39:47 — [discord] starting provider (@GYOZEN-AI)
• 23:39:51 — [discord] channels resolved (9 channels)
• (no "logged in" — 7 min gap)
• 23:46:20 — [health-monitor] restarting (reason: disconnected)
• 23:46:27 — [discord] logged in ✅ (2nd attempt works)

This did not occur on v2026.3.12. The issue is reproducible on every cold start.

OpenClaw version

2026.4.1

Operating system

Windows 11 Home

Install method

npm global

Model

claude-opus-4-6

Provider / routing chain

openclaw -> discord (discord.js gateway)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

23:39:42 [gateway] listening on ws://127.0.0.1:18789 (PID 19940)
23:39:47 [discord] starting provider (@GYOZEN-AI)
23:39:51 [discord] channels resolved (9 channels)
❌ No "logged in" message — hangs here
... 7 minute gap ...
23:46:20 [health-monitor] restarting (reason: disconnected)
23:46:27 [discord] logged in ✅ (2nd attempt)
23:46:33 [discord] native commands using Carbon reconcile path
23:46:34 [discord] awaiting gateway readiness → works

Impact and severity

No response

Additional information

No response