[BUG] Voice mode fails with "Voice connection failed. Check your network" on Windows (v2.1.74)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When activating voice mode via /voice (or holding Space), the mode appears to enable successfully ("Voice mode enabled. Hold Space to record"), but when attempting to use it, the following error is displayed:

Voice connection failed. Check your network and try again.

This occurs consistently — voice mode never connects. Network connectivity is otherwise fine (all other Claude Code features work normally, including API calls, web fetches, etc.).

This is not the same as #32249 (missing native audio module / audio-capture.node). The error here is specifically about the WebSocket voice connection failing, not about the audio capture module being unavailable.

What Should Happen?

Voice mode should establish a connection and allow push-to-talk voice input.

Error Messages/Logs

Voice connection failed. Check your network and try again.

No additional stack trace is shown to the user. The error message suggests a network issue, but all other network-dependent features work correctly.

Steps to Reproduce

1. Open Claude Code v2.1.74 in VS Code integrated terminal on Windows
2. Run /voice or start a session
3. Hold Space to record — voice mode shows "Voice mode enabled. Hold Space to record"
4. Attempt to record — error appears: "Voice connection failed. Check your network and try again."

Claude Model

Opus

Is this a regression?

I don't know

Claude Code Version

2.1.74 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

Environment details:

• Windows 11 Insider Preview (Build 26200.8037)
• Shell: Git Bash (MINGW64_NT-10.0-26200)
• Node.js: v22.21.1
• VS Code integrated terminal

Potentially related issues:

• #33383 — Voice mode not functioning on macOS/VSCode (403 WebSocket error)
• #31101 — Voice stream error: Connection closed: code 1006 (macOS)
• #32249 — Different issue: missing native audio module on Windows (not a network error)

The "Voice connection failed" error message appears to be a generic catch-all. It would be helpful if the underlying WebSocket error code or HTTP status (e.g., 403, 1006) were surfaced to aid debugging. Most existing voice issues are macOS-specific — this report adds Windows platform coverage.