# Problem with cursor skipping the questions

**URL:** <https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308>\
**Category:** Bug Reports\
**Tags:** rules, plan-mode\
**Created:** [June 29, 2026, 12:31pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308 "2026-06-29T12:31:50Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![skizadi\_yahoo](https://avatars.discourse-cdn.com/v4/letter/s/ec9cab/32.png) [@skizadi\_yahoo](https://forum.cursor.com/u/skizadi_yahoo)\
**Post date:** [June 29, 2026, 12:31pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/1 "2026-06-29T12:31:50Z")

</div>

### 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

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [June 29, 2026, 5:36pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/8 "2026-06-29T17:36:19Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![benr](https://avatars.discourse-cdn.com/v4/letter/b/73ab20/32.png) [@benr](https://forum.cursor.com/u/benr)\
**Post date:** [July 2, 2026, 4:24pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/10 "2026-07-02T16:24:35Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [July 3, 2026, 7:43pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/11 "2026-07-03T19:43:34Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [July 3, 2026, 7:45pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/12 "2026-07-03T19:45:32Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![danielfinke](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danielfinke/32/45791_2.png) [@danielfinke](https://forum.cursor.com/u/danielfinke)\
**Post date:** [July 13, 2026, 6:05pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/13 "2026-07-13T18:05:54Z")

</div>

Hey @kevinn, do you know if this fix is in stable now and if so, which version?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [July 17, 2026, 3:24pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/14 "2026-07-17T15:24:06Z")

</div>

@danielfinke This specific issue should have been fixed in 3.10.

---

<div class="post-metadata">

**Author:** ![Tom\_Bomer](https://avatars.discourse-cdn.com/v4/letter/t/f05b48/32.png) [@Tom\_Bomer](https://forum.cursor.com/u/Tom_Bomer)\
**Post date:** [October 22, 2026, 9:26am UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/16 "2026-10-22T09:26:00Z")

</div>

hey I am experiencing this issue in Agent mode, it doesn’t give me a chance to answer the Qs then says “you didn’t answer the Qs”

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [October 22, 2026, 12:17pm UTC](https://forum.cursor.com/t/problem-with-cursor-skipping-the-questions/164308/17 "2026-10-22T12:17:49Z")

</div>

Hey Tom,

Please raise a new thread, since this one was resolved in July!
