Voice mode doesn't initialize on session start when state persists from previous session
Resolved 💬 4 comments Opened Mar 11, 2026 by ImNyx4 Closed Apr 13, 2026
Description
When starting a new Claude Code session, /voice (hold-Space-to-record) doesn't work until toggled off and back on. The audio capture subsystem doesn't reinitialize on startup even though the voice mode state persists as "on" from the previous session.
Steps to Reproduce
- Enable voice mode with
/voicein a session - Use voice input normally (hold Space to record)
- End the session
- Start a new Claude Code session
- Try holding Space to record — nothing happens
Workaround
Run /voice twice:
- First
/voice→ "Voice mode disabled" (toggles stale state off) - Second
/voice→ "Voice mode enabled. Hold Space to record." (properly initializes)
After this, hold-Space-to-record works normally.
Expected Behavior
Either:
- Voice mode should fully initialize on session start when persisted state is "on" (i.e., the audio listener should start automatically), or
- Voice mode state should not persist across sessions, requiring a fresh
/voiceeach time
Environment
- macOS (Darwin 25.3.0, Apple Silicon)
- Claude Code CLI
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗