[BUG] Voice mode doesn't activate on session start despite voiceEnabled: true in settings
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?
Voice mode doesn't activate when starting a new Claude Code session, even though "voiceEnabled": true is saved in ~/.claude/settings.json. Holding Space bar types space characters instead of opening the voice recorder. Running /voice twice (off then on) restores functionality for that session.
What Should Happen?
Voice mode should be active immediately on session start when voiceEnabled: true is persisted in settings.json, without needing to toggle /voice off and on.
Error Messages/Logs
No error messages. The setting is correctly saved in ~/.claude/settings.json as "voiceEnabled": true, but the runtime voice state is not initialized from it on startup.
The only workaround is toggling /voice twice per session.
Steps to Reproduce
Steps to Reproduce
- Enable voice mode with /voice in a session
- Confirm "voiceEnabled": true is persisted in ~/.claude/settings.json
- Close the session and open a new one
- Hold Space bar — nothing happens (space characters are typed instead)
Expected: Voice mode should be active on session start since the setting is saved.
Actual: Voice mode is inactive. Space bar types spaces. Running /voice twice (off then on) restores it.
Environment: macOS (Darwin 25.1.0), Claude Code CLI
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.69 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗