Voice mode requires /voice twice to enable despite voiceEnabled: true in settings
Resolved 💬 3 comments Opened Mar 21, 2026 by toru-taaaaan Closed Apr 18, 2026
Description
When voiceEnabled: true is set in ~/.claude/settings.json, voice mode does not activate on session start. The user cannot hold Space to record until they manually run /voice.
However, since the internal state seems to think voice is already enabled, running /voice disables it first (outputs "Voice mode disabled."), requiring a second /voice to actually enable it ("Voice mode enabled.").
Steps to reproduce
- Set
"voiceEnabled": truein~/.claude/settings.json - Start a new Claude Code session
- Try holding Space to record → nothing happens
- Type
/voice→ outputs "Voice mode disabled." - Type
/voiceagain → outputs "Voice mode enabled. Hold Space to record."
Expected behavior
Voice mode should be active on session start when voiceEnabled: true is configured, or at minimum, the first /voice should enable it (not disable it).
Environment
- macOS 14.7.8 (Sonoma), Apple Silicon
- Language setting:
"language": "japanese"
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗