Problem with cursor skipping the questions

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

During the plan mode, Cursor ask questions.
But sometimes I am not at the desk for a while.
Then cursor skips my answers even if define a rule to tell it wait for me until i answer then continue to plan.
How could I solve this problem?

Steps to Reproduce

as above

Operating System

Windows 10/11

Version Information

Version: 3.9.8 (system setup)
VS Code Extension API: 1.105.1
Commit: 4aa8ff1b7877ed7bd01bcba308698f71a6735380
Date: 2026-06-25T01:39:30.490Z
Layout: editor
Build Type: Stable
Release Track: Default
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.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hi @skizadi_yahoo,

Thanks for reporting this. Cursor should wait for your answer here, so continuing while the question is still open is a bug. A custom rule cannot reliably prevent it because the waiting state itself can be lost after the question sits idle.

We have fixed the underlying issue, but that fix has not reached the current stable release yet. Please keep Cursor updated through Help > Check for Updates so you receive it when it ships (probably in a few days!)

If you want to get it sooner you can go to Beta in Cursor Settings and change your Release Track to Nightly but there’s no immediate need to do this unless you want to get it early!

Hey Kevin, this issue has been bothering me for a while so glad to hear it’s been fixed!

Just to confirm, will the fix prevent it from marking a question as “Skipped” if it’s idle waiting for a response for too long? And any idea when it’s hitting the stable release?

Thank you!

Hi @benr It’s in the nightly release currently! You can change to Nightly Release track by going to Cursor Settings → Beta and switching there. Stable probably next week.

@benr Yes, exactly, that’s the heart of the fix.

The fix addresses this in two ways:

  • It keeps the stream alive while a question is waiting on you, so being idle no longer triggers that timeout in the first place.
  • Even if a reconnect does happen for another reason, the question re-blocks and stays pending instead of being treated as skipped, so the agent won’t move on without your answer.