Audio (Voice Input) Button Disappears After Typing or Attaching Content

Ideas Feature Requests
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Bug Report: Audio Button Disappears

When I start a new chat in Cursor, the audio (voice input) button disappears as soon as I type text or attach any media/code. This prevents me from using voice input afterward.

Voice input is a very important feature for me—it’s faster and more convenient than typing long messages. Currently, once code or attachments are added, I can no longer explain things via audio.

Steps to Reproduce

  • Open a new chat
  • Type some text or attach any file/code
  • Audio (voice input) button gets hidden

Expected Behavior

The audio (voice input) button should always remain visible and usable in the chat, even after typing text or attaching files/code, so users can continue explaining or adding context via voice at any time.

Screenshots / Screen Recordings

Operating System

Windows 10/11
MacOS
Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.43
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.1.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

Hey, thanks for the report, you’re right: when you type text or attach files, the UI switches to manual input mode and the voice input button is hidden. This is the current UI behavior.

Your request makes sense: it would be convenient to combine text and voice input in the same message (for example, attach code and then explain by voice what you want to do with it).

I’ll pass this feedback to the dev team as a UX improvement request. For now, the only workaround is to use voice input before adding any text or files.

3

Upvoting this. It’s really a feature killer not being able to continue to use voice mode if there’s already text. Just keeping the button visible would solve the problem.