Voice mode broken on Windows v2.1.83 - spacebar types spaces, no audio capture

Resolved 💬 6 comments Opened Mar 25, 2026 by TalkingMonkeyOz Closed Apr 19, 2026

Environment

  • OS: Windows 11 Pro (10.0.26200)
  • Claude Code version: 2.1.83 (npm install)
  • Terminal: Windows Terminal + Git Bash
  • Shell: Git Bash (MINGW64)

Description

Voice mode (/voice) enables successfully and status bar shows "Voice: processing..." but holding spacebar does not record audio — it types spaces into the input instead.

This was also broken on v2.1.81. SoX 14.4.2 is installed (winget install ChrisBagwell.SoX) but does not appear to be used as a fallback on Windows (unlike Linux/macOS).

Steps to reproduce

  1. Launch Claude Code v2.1.83 on Windows 11 via npm
  2. Run /voice to enable voice mode
  3. Status bar shows "Voice: processing..."
  4. Hold spacebar — spaces are typed instead of recording audio
  5. No audio is captured

Expected behavior

Holding spacebar should activate the microphone and record speech for transcription.

Related issues

  • #31065 — native audio module not bundled for Windows
  • #30915 — audio-capture.node path hardcoded
  • #32249 — proposed SoX fallback for Windows
  • #33504 — voice command fails on Windows CLI
  • #38960 — space key moves cursor instead of recording

Workaround attempted

  • Installed SoX via winget install ChrisBagwell.SoX — no change
  • Tried rebinding push-to-talk key — no change
  • Downgraded to v2.1.81 — same issue

Notes

The npm-installed version on Windows appears to be missing the audio-capture.node native module entirely, and the SoX fallback path that exists for Linux/macOS is not wired up for Windows.

View original on GitHub ↗

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