crash voice chat
Dedicated thread for live voice call crashes / hard failures in Cursor IDE (not the parallel-agent overlap topic).
Prior events — Oct 23, 2026 (GMT-7):
Build: Cursor 3.27.12 (Universal), API 1.128.0, commit df132ffba90dfc15a12e6b8f020ba4e5d026c4b0.
— @nsdb
Voice chat crash — Oct 23, 2026
When: 9:31 PM GMT+7 — 4:31 PM UTC (2026-10-23T16:31:00Z).
What happened: Live voice chat crashed mid-session (call dropped abruptly). Single voice call, STRIPE workspace.
Build (Cursor → About): 3.27.12 (Universal); VS Code API 1.128.0; commit df132ffba90dfc15a12e6b8f020ba4e5d026c4b0; 2026-10-23T02:27:47.076Z; IDE / Stable / Default; Electron 42.11.16; Chromium 148.0.7778.280; Node 24.19.0; V8 14.8.178.38-electron.0; xterm.js 6.1.0-beta.291; Darwin arm64 25.6.0.
— NSDB
Hey @nsdb,
I looked at the calls from your account on Oct 23. Each drop (around 2:13, 2:49, 5:48 and 9:31 PM your time) happened because the voice service closed the line from its side, and Cursor ended the call rather than reconnecting it. The 5:48 PM and 9:31 PM calls ended exactly two hours after they connected: a single live voice session currently has a two-hour limit, and the call ends when it is reached instead of carrying on. The earlier two drops happened well before that limit, and the team is looking into why the line was closed there.
In the meantime, starting a new call right after a drop should get you going again. For long sessions, it can help to plan a fresh call before the two-hour mark.
For the 5:05 PM call where the voice repeated itself and cut itself off, the call itself stayed connected, and it looks like the voice kept detecting someone talking over it. That usually happens when the agent’s own voice from your speakers is picked up by the microphone. Could you try a call with headphones and let me know whether the self-interrupting still happens? It would also help to know whether you were using speakers or headphones on Oct 23.