Chat goes into a soft lock if you don't respond to an “Asking Question” for a long time

[Artemonim]

Describe the Bug

Chat goes into a soft lock if you don’t respond to an “Asking Question” for a long time. I left Chat in waiting for a question overnight. In the morning, I typed a prompt without selecting any answers and sent it.

The message was accepted, but the send button did not change to a “Stop” icon, and no call entry appeared on the Dashboard. I tried clicking the send button again; a waiting message for the model’s response appeared, and an entry showed up on the Dashboard, but the model still didn’t respond.

I stopped the request and tried again (prompt-2). It didn’t work. At the same time, I tried in another chat, and the model responded instantly.

Cursor restart helped.

Steps to Reproduce

You’ll probably need to leave the chat in a “waiting for a response” state for several hours.

You may also notice that, 6.5 hours later, there’s a request (prompt-1) on Danboard from the same model that I didn’t make - perhaps the chat broke down at that moment.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.15.1 (system setup)
VS Code Extension API: 1.128.0
Commit: 41c5e281845de0ce890a8053a3874064bfbdb8b0
Date: 2026-08-04T06:41:23.990Z
Layout: IDE
Build Type: Stable
Release Track: Nightly
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Windows_NT x64 10.0.22631

For AI issues: which model did you use?

K3 Max

For AI issues: add Request ID with privacy disabled

885af539-3a36-47f5-83d8-249f92ff026d Privacy On

Does this stop you from using Cursor

Yes - Cursor is unusable

[mohitjain (Mohit)]

Hey there!

This isn’t intended behavior, and it’s nothing on your end. When an “Asking Question” sits unanswered for a long time, that chat’s connection goes stale in the background, so a new message in it won’t kick off a fresh response until you reset it. That’s why the send button never turned into Stop, and why a full restart fixed it.

Faster ways to recover than a full restart:

• Command Palette (Ctrl+Shift+P) → Developer: Reload Window
• Or just start a new chat for that task - it’s isolated to the one stuck session

If you’ll be stepping away, answering or stopping the “Asking Question” first avoids it. And that extra request ~6.5h later that you didn’t make is the app trying to re-establish the stalled session, not something you triggered.

This is an issue we’re tracking and the team is already looking into it. No timeline to share, but I’ll follow up here when there’s an update - and since you’re on Nightly, staying current will get you the fix as it lands.