Voice mode state not preserved correctly across sessions
Resolved 💬 5 comments Opened Mar 15, 2026 by adamgfraser Closed Apr 17, 2026
Problem
When voice mode is enabled in a session and the user exits and starts a new session:
- Voice mode appears to be "enabled" (carried over from settings) but doesn't actually work
- When the user types
/voiceto fix it, it disables voice mode (toggling the stale "on" state to off) - The user has to type
/voicea second time to actually enable working voice mode
Expected Behavior
Either:
- Voice mode state should be properly restored and functional when starting a new session, OR
- Voice mode should start fresh (disabled) in each new session so a single
/voiceenables it
Current Behavior
The state is half-preserved — the toggle thinks it's "on" from the previous session, but the actual voice functionality isn't connected. This means /voice toggles it to "off" first, requiring a double-toggle to get working voice mode.
🤖 Generated with Claude Code
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗