openclaw - 💡(How to fix) Fix Discord voice: @discordjs/voice MODULE_NOT_FOUND after v2026.3.28 update + voice.tts config breaking change [1 participants]

Bug Description

After updating to v2026.3.28, Discord voice joining fails with Cannot find module '@discordjs/voice'. Additionally, the channels.discord.voice.tts config schema changed in a breaking way without migration or changelog notice.

Issue 1: @discordjs/voice not resolvable from runtime context

Error:

[EventQueue] Listener DiscordVoiceReadyListener failed for event READY:
Error: Cannot find module '@discordjs/voice'
Require stack:
- /path/to/openclaw/dist/manager.runtime-gd1YL1MK.js

Root cause: The @discordjs/voice package (v0.19.2) and related dependencies (opusscript, prism-media, @snazzah/davey) are installed under dist/extensions/discord/node_modules/, but the voice manager runtime (manager.runtime-*.js) runs from the dist/ root directory. Node.js require() resolution cannot find these packages from the root context.

Dependency report (from generateDependencyReport()):

@discordjs/voice: 0.19.2        ✅ (but only in extensions subdir)
prism-media: 1.3.5              ✅
opusscript: 0.1.1               ✅
@snazzah/davey: 0.1.10          ✅
ffmpeg: 6.1.1 + libopus         ✅
native crypto aes-256-gcm       ✅

All packages exist under dist/extensions/discord/node_modules/ but are not accessible from dist/manager.runtime-*.js.

Workaround: Creating symlinks from the root node_modules/ to the extensions subdirectory:

cd /path/to/openclaw
mkdir -p node_modules/@discordjs node_modules/@snazzah
ln -sf ../../dist/extensions/discord/node_modules/@discordjs/voice node_modules/@discordjs/voice
ln -sf ../../dist/extensions/discord/node_modules/@snazzah/davey node_modules/@snazzah/davey
ln -sf ../../dist/extensions/discord/node_modules/@snazzah/davey-linux-x64-gnu node_modules/@snazzah/davey-linux-x64-gnu
ln -sf ../dist/extensions/discord/node_modules/opusscript node_modules/opusscript
ln -sf ../dist/extensions/discord/node_modules/prism-media node_modules/prism-media

⚠️ This workaround is lost on every npm install / update.

Issue 2: voice.tts config breaking change

Previous config (worked in v2026.3.13):

"voice": {
  "tts": {
    "provider": "openai",
    "openai": {
      "voice": "nova"
    }
  }
}

Error on v2026.3.28 startup:

channels.discord.voice.tts: Unrecognized key: "openai"

The gateway refuses to start with the old config. The new schema expects provider-specific settings under a providers key:

"voice": {
  "tts": {
    "provider": "openai",
    "providers": {
      "openai": {
        "voice": "nova"
      }
    }
  }
}

Impact: The gateway fails to start entirely with the old config — requires manual config editing to recover.

Expected Behavior

1. Voice dependencies should be resolvable from the runtime context without manual symlinks
2. Config schema changes should either auto-migrate old formats or provide a clear migration error message (not a generic "Unrecognized key")

Environment

• OpenClaw version: 2026.3.28
• Previous version: 2026.3.13
• OS: Ubuntu 24.04 (x64)
• Node.js: v25.4.0
• Install method: npm install -g openclaw