[FEATURE] Voice mode should work in confirmation and selection prompts

Resolved 💬 4 comments Opened Apr 2, 2026 by CMahrt Closed Apr 6, 2026

Preflight Checklist

  • [ ] 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

When Claude Code presents a confirmation prompt (y/n) or a numbered selection (e.g., "1, 2, or 3"), voice mode input
is not available. The user is forced to switch to keyboard input, which breaks the workflow.

Proposed Solution

Voice mode should remain active during confirmation and selection prompts. Saying "yes", "no", "1", "2", etc. should
be recognized and accepted as valid input — these are short, unambiguous responses that speech-to-text handles
reliably.

Why this matters

Switching between voice and keyboard mid-conversation disrupts the flow, especially for users who primarily rely on
voice input. There is no technical reason why these prompts should be text-only — the expected inputs are simple and
well-defined.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

Other

Use Case Example

Example:

  1. Enable voice mode
  2. Trigger any action that requires confirmation (e.g., a tool call that needs approval)
  3. Try to respond via voice → input is not accepted
  4. User must type the response manually

Additional Context

I was unable to check for duplicates — searching for 'voice' returns hundreds of results, making it impractical to
verify.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗