openclaw - 💡(How to fix) Fix [Bug]:Discord /voice list returns no usable voices; /voice chat stays status-only (no outbound audio)

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

On Discord, /voice does not provide a usable voice-selection flow and does not generate outbound audio replies.

Root Cause

On Discord, /voice does not provide a usable voice-selection flow and does not generate outbound audio replies.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Summary

On Discord, /voice does not provide a usable voice-selection flow and does not generate outbound audio replies.

Environment

  • OpenClaw: 2026.5.7
  • Surface: Discord
  • Gateway: local
  • Restarted gateway multiple times during testing

Config changes tested

  1. Set Talk provider to system + restart
  2. Set Talk provider to microsoft + restart

Current /voice status

  • provider: microsoft
  • talk.providers.microsoft.voiceId: unset
  • microsoft.apiKey: unset

Repro steps

  1. Run /voice status
  2. Run /voice list 3.3. Run /voice chat Audio reply test from Jaime

Actual behavior

  • /voice status returns status text.
  • /voice list does not return a usable voice list in this Discord flow.
  • /voice chat ... returns status-like/ephemeral output instead of outbound audio.

Expected behavior

  • /voice list should return selectable voices (or a clear fallback).
  • /voice chat <text> should generate outbound audio reply in-channel.

Evidence

Screenshots captured for each step (status/list/chat result) and available on request.

Steps to reproduce

Steps to reproduce

  1. In Discord, run /voice status.
  2. Run /voice list.
  3. Run /voice chat Audio reply test from Jaime.
  4. Observe: no usable voice list and no outbound audio reply.

Expected behavior /voice list returns selectable voices (or clear fallback), and /voice chat <text> sends an audio reply in-channel.

Actual behavior /voice status prints provider state, /voice list is not usable in this flow, and /voice chat returns status-like/ephemeral output instead of audio.

Expected behavior

Yep — the template still has placeholder Telegram text. Replace with this exactly:

Expected behavior In Discord, /voice list should return selectable voices (or a clear fallback), and /voice chat <text> should send an outbound audio reply in-channel.

Actual behavior

Observed in Discord: /voice status returns provider state (provider: microsoft, voiceId: unset, apiKey: unset). /voice list does not return a usable voice list. /voice chat Audio reply test from Jaime returns status-like/ephemeral output instead of audio.

OpenClaw version

2026.5.7

Operating system

macOS 26.4.1 (arm64)

Install method

pnpm (OpenClaw CLI/gateway local install)

Model

openai-codex/gpt-5.3-codex

Provider / routing chain

openclaw gateway -> OpenAI (direct)

Additional provider/model setup details

Issue reproduced on Discord /voice commands. Talk provider switched from system to microsoft; gateway restarted after each change. /voice status updates correctly, but /voice list remains unusable and /voice chat returns status-like/ephemeral output instead of outbound audio.

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Yep — the template still has placeholder Telegram text. Replace with this exactly:

Expected behavior In Discord, /voice list should return selectable voices (or a clear fallback), and /voice chat <text> should send an outbound audio reply in-channel.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING