[BUG] Voice mode not initiated on startup unless toggled off/on despite being TRUE

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?

During a new Claude Code process (as in PID, not fresh context after /clear alone), holding SPACE does not record voice despite voice mode being TRUE in settings. Instead, many SPACE characters are typed into the message field as long as the key is pressed.

Toggling /voice shows that it switches to FALSE; so the application recognizes it was set to TRUE but does not seem to actually activate voice mode unless it's toggled off and then back on.

What Should Happen?

When /voice is TRUE, holding SPACE in a new Claude Code PID should always render a transcription.

Error Messages/Logs

Steps to Reproduce

1. Toggle /voice in a Claude Code session such that you get the response Voice mode enabled. Hold Space to record.
2. End the Claude Code process by closing the terminal window. Gracefully exiting by /exit may also reproduce this behavior, but I've been ending the process by closing the active terminal window.
3. Reopen Claude Code.
4. Hold SPACE.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.80

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

GNOME terminal.
Related but separate issues:

• #33580 — voice mode not available (feature flag issue)
• #30904 — voice enabled flag hardcoded to false in v2.1.69