[FEATURE]

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

I primarily use Claude Code in the terminal with Voice Mode in tap mode. My workflow is to tap once to start listening, then browse the repository while continuously dictating my thoughts, search terms, and instructions.

Occasionally, Voice Mode stops recording unexpectedly while I'm navigating the codebase. Since there is no persistent indication of the recording state, I continue speaking, assuming Claude is still listening. I often don't realize recording has stopped until much later, which means part of my dictation is lost.

Proposed Solution

Add a persistent Voice Status indicator to the Claude Code terminal UI whenever Voice Mode is enabled.

For example:

🎙️ Listening – actively recording
⏸️ Idle – Voice Mode enabled but not currently recording
⚠️ Recording Stopped – recording ended unexpectedly
🔇 Voice Disabled

The status should always be visible so that, while navigating the repository, I can immediately tell whether Claude is still listening.

Alternative Solutions

Currently, I have to periodically look back at the terminal input area to verify that Voice Mode is still recording, which interrupts my workflow. If I suspect recording has stopped, I manually restart Voice Mode and repeat the portion I was dictating. This works, but it's easy to miss and results in lost dictation when I'm focused on navigating the repository.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Example scenario:

1. I start Voice Mode in tap mode with a single tap.
2. I begin exploring a Rails codebase, opening models, controllers, and services while describing what I want Claude to implement.
3. As I browse the repository, I dictate search terms, observations, and implementation details without looking at the terminal input.
4. Voice Mode stops recording unexpectedly, but there is no persistent indication that it has stopped.
5. I continue speaking for another minute or two, assuming Claude is still listening.
6. When I return to the prompt, I realize only part of my instructions were captured and I have to repeat everything from memory.

A persistent voice status indicator would immediately show that recording had stopped, allowing me to resume recording before losing any dictated instructions.

Additional Context

This is particularly useful for users who use Voice Mode as a hands-free coding workflow. I frequently start a recording, navigate through multiple files, search the repository, and dictate keywords, observations, and implementation details as I go. Because my attention is on the code rather than the input prompt, it's easy to miss that recording has stopped.

A persistent voice status indicator would make this workflow much more reliable and prevent losing dictated instructions.

Environment
Claude Code (Terminal)
Voice Mode: Tap
macOS