PR #73714: fix(discord): gate GuildVoiceStates intent on voice.enabled (#73709)

• Repository: openclaw/openclaw
• Author: hclsys
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/73714

Description (problem / solution / changelog)

What

Fixes #73709. resolveDiscordGatewayIntents unconditionally OR'd GatewayIntents.GuildVoiceStates into the requested intent bitmask regardless of channels.discord.voice.enabled. The result: a sustained ~100% CPU spin in the gateway process on Linux (Hetzner CPX31, 4 vCPU AMD confirmed) and ~20-33% on macOS (Apple Silicon Mac Studio) at idle, because the Discord gateway kept dispatching voice-state events that nothing consumed when voice was meant to be off.

Fix

Pass the existing discordConfig.voice config through to the intent resolver and gate GuildVoiceStates on voice.enabled !== false:

if (voiceConfig?.enabled !== false) {
  intents |= carbonGateway.GatewayIntents.GuildVoiceStates;
}

Default behavior is unchanged — channels.discord.voice.enabled defaults to true, so the intent stays on for the common case. Operators who explicitly set voice.enabled: false (text-only Discord channel) now get a true text-only gateway connection without the CPU spin.

Why this shape rather than a new intents.voiceStates opt-in

The issuer's suggested local patch (in #73709) introduces a new channels.discord.intents.voiceStates opt-in field. That works, but:

• Adding a new field requires a corresponding zod-schema.providers-core.ts strict-schema update.
• It splits the user's intent across two config knobs (voice.enabled: false AND intents.voiceStates: false to actually go quiet).
• Reusing the existing voice.enabled config the user already sets keeps the contract minimal and matches the user's actual mental model (turn off voice → no voice traffic).

Pre-implement audit

1. Existing-helper check (vincentkoc #57341). Chose to reuse the existing voice.enabled config rather than introduce a new helper / config field. Saves a schema change. ✅
2. Shared-helper caller check (steipete #60623). resolveDiscordGatewayIntents is exported from runtime-api.ts but only called from one in-tree site (gateway-plugin.ts:489); adding an optional second parameter is backward-compatible — external callers that pass only the first arg get the same default behavior (voice on). ✅
3. Broader-fix rival scan (steipete #68270). Zero rival PRs reference #73709. ✅

Verified locally

npx oxlint extensions/discord/src/monitor/gateway-plugin.ts extensions/discord/src/monitor/gateway-intents.test.ts
# Found 0 warnings and 0 errors.

npx vitest run extensions/discord/src/monitor/gateway-intents.test.ts
# Tests  4 passed (4)

Tests cover:

• Default (no args) → GuildVoiceStates set
• voice.enabled: true → GuildVoiceStates set
• voice.enabled: false → GuildVoiceStates cleared, base text intents preserved
• Privileged intents (presence, guildMembers) layer independently of voice

lobster-biscuit: 73709-discord-voice-states-intent-gate

Sign-Off:

• I have read and agree to the OpenClaw Contributor License Agreement.

Changed files

• CHANGELOG.md (modified, +1/-0)
• extensions/discord/src/monitor/gateway-intents.test.ts (added, +59/-0)
• extensions/discord/src/monitor/gateway-plugin.ts (modified, +13/-3)