claude-code - 💡(How to fix) Fix [Feature Request] Native text-to-speech output for Claude Code responses [2 comments, 2 participants]

Description

Claude Code has /voice for speech-to-text input, but there's no native way to have responses read aloud. This was previously requested in #2189 (auto-closed due to inactivity, not resolved).

Use case

Claude Code's output is detailed and thorough — which is great — but it's often too long and generated too fast for me to keep up with by reading. I'm a slow reader and don't have the patience to scroll through walls of text after every response. The information is valuable, I just can't absorb it visually at that pace.

I'm used to listening to audiobooks at 2x speed. If Claude Code could read its responses aloud with configurable playback speed, I could effortlessly absorb all that detail while continuing to work. I'd actually want the verbose output instead of skimming past it.

Important: I don't need voice input. I love typing my instructions — I'm usually surrounded by people when I work, so speaking to Claude Code isn't practical. What I need is the opposite direction: text input, audio output. Just let me type my request, put on my headphones, and listen to what Claude did and why — without having to read a novel every time.

Proposed implementation

• A /speak toggle or --tts flag that reads responses aloud
• Configurable reading speed (1x, 1.5x, 2x, etc.) — critical for power users who are used to fast audio consumption
• Use system TTS by default (say on macOS, espeak on Linux, SAPI on Windows)
• Option for streaming TTS (read as tokens arrive, not wait for full response)
• Configurable via settings.json (voice, speed, on/off)
• Ability to pause/resume/skip with a keybinding

Why native matters

Community MCP plugins exist (VoiceMode, mcp-voice-hooks, claude-code-tts) but they require extra setup, API keys, or dependencies. A native integration would:

• Make verbose output accessible: Users who can't keep up reading would finally benefit from Claude Code's detailed explanations
• Lower the barrier: works out of the box, like /voice does for input
• Complete the interaction loop: text input + audio output is a valid and practical interaction mode, especially in shared/open office environments
• Enable multitasking: listen to explanations through headphones while reviewing the actual code changes

The core problem

Claude Code gives excellent detail in its responses, but the only way to consume it is by reading. For users who process audio faster than text — or who simply can't read as fast as Claude generates — all that useful context goes to waste. TTS output with speed control would turn a frustration into a superpower.

The /voice feature assumes people want to talk to Claude. But some of us want Claude to talk to us — while we keep typing. These are independent needs.

Prior art

• #2189 (auto-closed, community interest existed)
• /voice already proves Anthropic values voice interaction
• Multiple community plugins confirm demand for this feature