voiceEnabled setting in settings.json doesn't persist across sessions
Resolved 💬 3 comments Opened Mar 13, 2026 by RobertJLora Closed Mar 17, 2026
Description
voiceEnabled: true is set in ~/.claude/settings.json, but voice mode does not auto-enable when starting a new chat session. Users must manually run /voice at the start of every conversation to activate it.
Expected behavior
If voiceEnabled: true is set in settings.json, voice mode should be active automatically when a new session starts -- no need to toggle it manually each time.
Current behavior
voiceEnabled: trueexists in~/.claude/settings.json- Starting a new chat requires running
/voiceto enable voice mode - Voice mode disables itself after each session ends
- The setting appears to have no effect on session initialization
Additional context
- There's also no
--voiceCLI flag to launch with voice enabled - The
/voicecommand works fine within a session -- the issue is purely about persistence across sessions - Voice key binding (Space, hold-to-record) is not customizable either, but that's a separate feature request
Environment
- macOS (Darwin 25.3.0)
- Claude Code CLI
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗