[FEATURE] Voice input support for edit confirmation prompts

Resolved 💬 3 comments Opened Mar 19, 2026 by Nadia-JSch Closed Apr 17, 2026

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

When using Claude Code's /voice mode, voice input only works in the main chat prompt. When Claude proposes a file edit and displays a confirmation dialog/prompt, there is no way to respond using voice — you are forced to switch back to typing. This breaks the voice-first workflow and is especially frustrating for users who rely on voice input for accessibility or productivity reasons.

Proposed Solution

Voice input should be supported in edit confirmation dialogs when selecting 'No' and explaining why the edit was rejected. Ideally, pressing the push-to-talk key (e.g. Space) should activate voice input regardless of which prompt is currently focused.

Alternative Solutions

Currently, selecting 'No' on the pop-up and then explaining why in the main CLI interface.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

  1. Claude proposes an edit to a file and displays a confirmation prompt.
  2. I want to reject the edit and explain what to change in voice mode. This saves me time typing

Additional Context

<img width="2124" height="524" alt="Image" src="https://github.com/user-attachments/assets/25a8e0ec-a3f0-4269-9c4b-3f2e6bbe0f37" />

View original on GitHub ↗

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