Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Discord plugin loads and resolves guild/channel/user IDs, but the Discord client stays at "awaiting gateway readiness" and never reaches READY on Windows.

Steps to reproduce

1. Start OpenClaw 2026.5.3-1 on Windows with the Discord plugin enabled.
2. Run openclaw gateway restart.
3. Wait at least 120 seconds.
4. Run openclaw gateway probe.
5. Check the gateway log.

Expected behavior

Discord should reach gateway READY, and openclaw gateway probe should complete without the read probe timing out.

Actual behavior

Gateway becomes reachable/admin-capable, and Discord resolves guild/channel/user IDs, but Discord remains at awaiting gateway readiness. After waiting 120 seconds, openclaw gateway probe still reports Read probe: failed - timeout.

OpenClaw version

2026.5.3-1

Operating system

Windows

Install method

npm global

Model

openai-codex/gpt-5.5

Provider / routing chain

OpenClaw gateway with OpenAI Codex model

Additional provider/model setup details

NOT_ENOUGH_INFO

Logs, screenshots, and evidence

Observed logs:
- [gateway] http server listening (7 plugins: browser, device-pair, discord, memory-core, phone-control, talk-voice, telegram)
- [gateway] gateway ready
- [discord] channels resolved: 1476427990618607721
- [discord] channel users resolved: 1021989512227868814
- [discord] client initialized as 1476275479047700564; awaiting gateway readiness

After 120s:
openclaw gateway probe:
- Reachable: yes
- Capability: admin-capable
- Connect: ok
- Read probe: failed - timeout

Tried:
- openclaw doctor --fix
- installed discord plugin
- increased channels.discord.gatewayReadyTimeoutMs to 120000
- increased channels.discord.gatewayRuntimeReadyTimeoutMs to 120000

Related closed issue:
https://github.com/openclaw/openclaw/issues/53132

This appears similar to #53132, but still reproduces on Windows with OpenClaw 2026.5.3-1.

Impact and severity

Affected: Discord channel integration on this Windows OpenClaw gateway.
Severity: High, because Discord messages cannot reliably connect through the gateway.
Frequency: Reproduced after restart and waiting 120 seconds.
Consequence: Discord integration remains unusable even though the gateway itself is reachable.

Additional information

The local gateway is reachable/admin-capable, so the failure appears specific to Discord gateway readiness or follow-up read diagnostics rather than the HTTP gateway listener itself.