Questionnaire timeout falsely treated as “skipped”; multi-chat rollback affects other chats

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Bug 1 — Agent questionnaire / prompt countdown
During an Agent conversation, the UI sometimes shows a questionnaire or structured prompt from the Agent, with what appears to be a countdown. If I do not submit an answer before the countdown finishes—even though the questionnaire remains visible on screen—the Agent proceeds as if I skipped the questionnaire instead of still being able to respond.

Bug 2 — Rollback in one chat affects another chat’s applied edits
When using multiple chats in parallel and both conversations produce or apply code changes, performing a rollback / undo of applied changes in one chat can also undo edits that were already applied from a different chat.

Steps to Reproduce

Bug 1

Start an Agent conversation where the Agent presents a questionnaire or multi-choice prompt.
Leave the questionnaire on screen without selecting/submitting until the countdown completes (or appears to expire).
Observe whether the Agent treats the interaction as skipped even though the UI still showed the questionnaire.

Bug 2

Open Chat A and apply code changes via the Agent (accept/apply edits as you normally would).
Open Chat B (another conversation) and also apply code changes, possibly touching overlapping files.
In Chat A, use rollback / undo for that conversation’s applied changes.

Operating System

Windows 10/11

Version Information

Version: 3.2.16 (system setup)
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
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: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Thanks for the detailed report on both issues.

Bug 1 (countdown timeout): This is a known issue. The agent can sometimes proceed after a prompt or approval times out, even though the UI still shows it. Our team is actively investigating this behavior. Updating to the latest Cursor version may help, as some improvements in this area have shipped since your build (April 28). You can update via Help > Check for Updates or the Command Palette (Attempt Update).

Bug 2 (cross-chat rollback): This is a known limitation of how checkpoints currently work. For now, the safest approach is to avoid overlapping file changes across parallel chats, or to commit/stash changes from one chat before reverting another.

Could you also try updating to the latest version and let us know if Bug 1 still occurs? That would help us narrow down whether the specific fix that shipped addresses your case.