Microphone bug in Agent window with ˆm hotkey

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Bug in the Agent Window microphone recording capability (via hotkey only).

Starting a recording via the hotkey (ˆm) is leading to an automatic completion trigger at the 30s mark.

Reproduction: hotkey pressed and maintained, speech starts, at the 30s mark, recording ends and loads to process text, text appears, 1-3s have elapsed with uncaptured speech, recording continues until next 30s with another interruption and text appended.

This has been verified to be exclusive to the hotkey. Clicking on the mic button to trigger a recording does not create any issues. The editor recording doesn’t have this issue either.

Thank you!

Steps to Reproduce

Simply start recording with hotkey ˆm and maintain for over 30s.

Operating System

MacOS

Version Information

Version: 3.2.21 (Universal)
VSCode Version: 1.105.1
Commit: 806df57ed3b6f1ee0175140d38039a38574ec720
Date: 2026-05-03T01:46:14.413Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. The symptom and steps are clear. This isn’t intended behavior for long dictations. In Hold to Talk Ctrl+M, there’s a 30s safety timer that’s meant to protect against a stuck key, but if you actually hold it for more than 30s it restarts the session and drops speech at the boundary. Clicking the mic and editor dictation don’t use this hold mode, so they aren’t affected.

I’ve logged a bug for the Glass team. I can’t share an ETA yet, but I’ll post an update in the thread as soon as I have one.

Workaround for now:

  • Use the mic button toggle mode, no 30s limit there. It has a 5-minute per session cap.