openclaw - 💡(How to fix) Fix [Bug]: Discord `/vc join` hears/transcribes speech but returns no spoken reply; voice session uses `tts` + `NO_REPLY`, gateway logs `No reply from agent.` [1 participants]

Summary

Native Discord voice joins successfully and inbound speech is transcribed correctly, but no audible reply is played. In the voice session transcript, the agent calls the tts tool and then ends with NO_REPLY. The Discord voice runtime then logs [discord] No reply from agent. and plays nothing.

This appears distinct from the known DAVE/decrypt failures because in this case:

• join succeeds
• inbound speech is captured
• STT works
• the failure happens in the response/output path

Environment

• OpenClaw: 2026.4.2
• Host: macOS
• Channel: Discord
• Native Discord voice enabled via channels.discord.voice.enabled = true
• Old discord-voice plugin disabled in config:
  • plugins.entries.discord-voice.enabled = false

Relevant config state

• channels.discord.voice.enabled = true
• plugins.entries.discord-voice.enabled = false
• commands.native = auto
• global TTS configured and working outside this path
• no obvious mismatch with official docs for native Discord voice setup

What works

• /vc join is available
• bot joins the voice channel successfully
• bot remains connected
• inbound user speech is captured and transcribed correctly

What fails

• bot does not produce audible voice replies
• gateway logs:
  • [discord] No reply from agent.

Exact observed behavior

During native Discord voice tests, the captured voice session transcript shows:

• user speech is transcribed correctly from multiple direct test prompts
• then the assistant calls the tts tool
• then the turn ends with NO_REPLY
• Discord voice runtime logs [discord] No reply from agent.
• no playback occurs in VC

Evidence

Voice-only session evidence was confirmed from the local session transcript and gateway logs.

Observed gateway log timestamps:

• 16:39:03 — [discord] No reply from agent.
• 16:43:32 — [discord] No reply from agent.
• 16:43:38 — [discord] No reply from agent.
• 16:52:29 — [discord] No reply from agent.

Why this looks like a runtime bug

The failure is not in join or STT:

• Discord VC join works
• inbound audio is transcribed correctly
• the failure is that the response path produces no final text payload for Discord voice playback

There also appears to be an implementation asymmetry:

• the dedicated voice-call pathway has an explicit spoken-output contract (VOICE_SPOKEN_OUTPUT_CONTRACT)
• the Discord voice runtime path in manager.runtime-Ct8g7s7u.js does not appear to apply an equivalent spoken-output contract before calling the agent

That may allow the agent to choose tool-based audio output (tts) plus NO_REPLY, which makes sense for some channels/tools but breaks the built-in Discord voice playback path, which seems to expect reply text.

Suspected root cause

Native Discord voice is allowing the agent to produce output in the wrong mode for VC playback:

• agent uses tts
• final payload becomes empty / silent token path
• Discord voice runtime sees no reply text and logs No reply from agent.

Repro steps

1. Enable native Discord voice:
   • channels.discord.voice.enabled = true
2. Disable old Discord voice plugin:
   • plugins.entries.discord-voice.enabled = false
3. Restart gateway
4. In Discord, run /vc join
5. Speak a direct test prompt asking for a spoken reply
6. Observe:
   • VC join succeeds
   • no audible response
   • gateway logs [discord] No reply from agent.
   • session transcript shows speech was transcribed correctly

Expected behavior

• bot should generate a spoken reply and play it in the voice channel

Actual behavior

• speech is heard/transcribed
• no audible reply is played
• session shows tts tool usage + NO_REPLY
• gateway logs [discord] No reply from agent.

Notes

This appears different from the earlier Discord voice DAVE/decrypt issues because inbound speech capture is already working in this repro. The breakage seems to be specifically in the response/playback contract for native Discord voice.