Voice mode fails to access audio device on WSL2 + WSLg (Windows 11)

Resolved 💬 2 comments Opened May 8, 2026 by Konrad-Wawryniuk-Sii Closed May 12, 2026

Description

/voice reports "Voice mode could not access an audio device in WSL" despite PulseAudio being fully functional via WSLg.

Environment

  • OS: Windows 11
  • WSL: WSL2 with WSLg active
  • Claude Code: v2.1.133

Audio setup

  • PulseAudio server running at unix:/mnt/wslg/PulseServer
  • PULSE_SERVER=unix:/mnt/wslg/PulseServer correctly set in environment
  • RDPSource present (status: SUSPENDED — normal when idle, activates on use)
  • Default Windows input device: Realtek Microphone Array (Status: OK)
  • parecord successfully captures audio

Steps to reproduce

  1. Open Claude Code in WSL2 terminal on Windows 11
  2. Type /voice

Expected behavior

Voice dictation activates and uses the PulseAudio RDPSource forwarded via WSLg.

Actual behavior

Voice mode could not access an audio device in WSL. WSL2 with WSLg (Windows 11) provides audio via PulseAudio — if you are on Windows 10 or WSL1, run Claude Code in native Windows instead.

Additional context

parecord can record successfully, confirming the mic and PulseAudio stack work. The issue is in how Claude Code opens the audio device, not the WSLg infrastructure.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗