[FEATURE] Auto-enable voice mode at session start (persist /voice toggle across sessions)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

The current voice mode implementation requires typing /voice manually at the start of every new Claude Code session. This defeats the purpose of a hands-free workflow — if I want to code by voice, I still have to reach for the keyboard just to enable voice mode before I can begin.

The "voiceEnabled": true setting in settings.json exists but only controls feature availability, not auto-activation. There is no way to make voice mode the default active state when a session opens.

Use Case Example:

1. I open Claude Code to work on my CRM codebase
2. I want to describe a refactor verbally ("move all lead qualification logic into a dedicated service")
3. Currently: I must type /voice, then hold spacebar, then speak
4. With voiceAutoStart: I open Claude Code, hold spacebar immediately, and start talking
5. This matters most for long coding sessions where voice is the primary interaction — the manual /voice step is a constant friction point that breaks the hands-free mental model

Priority: High — this is a daily friction point for anyone using voice as their primary input mode

Feature Category: Voice / Settings / Session Lifecycle

Proposed Solution

Add a "voiceAutoStart": true setting to settings.json (user-level and/or project-level) that automatically activates voice mode when a new session begins — equivalent to having /voice run automatically on SessionStart.

Ideal behavior:

• User sets "voiceAutoStart": true in ~/.claude/settings.json
• Every new Claude Code session opens with voice mode already active (spacebar push-to-talk ready immediately)
• No need to type /voice manually
• The existing /voice toggle still works to turn it off mid-session if needed

Additional Context:

• The "voiceEnabled": true key already exists in settings.json — this request is specifically for an auto-activation flag, not for enabling the feature itself
• Analogous to how terminal emulators let you set a default profile that auto-starts with specific modes active
• Related: SessionStart hooks could be a natural integration point if slash commands were invokable from hooks

Alternative Solutions

• VoiceMode MCP server (getvoicemode.com) — community workaround, but adds external dependency for what should be a native setting
• SessionStart hooks — hooks only run shell commands, not Claude Code slash commands, so /voice cannot be triggered this way
• Typing /voice at the start of every session — current workaround, breaks the hands-free workflow from the start

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_