Wait confirmation window not visible

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

During a conversation, if a terminal command requiring confirmation is neither accepted nor declined, the chat enters a “disabled” or “pending confirmation” state.

After that, the chat session becomes partially blocked: no confirmation prompt is visible anymore, so it is impossible to approve or reject the pending command. As a result, the only workaround is to start a new chat session.

While this happens, the chat history appears greyed out. In some cases, it is possible to exit this state, but the method is unclear and not reproducible.
Other side effect: it is no longer possible to edit previous user messages.

Steps to Reproduce

On Windows:

Enter a prompt that triggers a terminal command requiring confirmation.

Without accepting or declining the command, type another message in the chat.

Result: command validation becomes blocked, and no confirmation prompt is shown.

Expected Behavior

The “run command” window, in which you can accept or decline a command, is no longer visible.

Screenshots / Screen Recordings

reproducing_issue
reproducing_issue888×812 30.7 KB

chat_stuck.png
chat_stuck.png890×779 25.1 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.35 (system setup)
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120
Date: 2026-01-13T07:39:18.564Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Sonnet 4.5

For AI issues: add Request ID with privacy disabled

9a0df287-9c54-4442-a988-4262dd40c9a8

Additional Information

The current chat window is almost no longer usable. All you can do is try to save your context and continue in a different chat window.
The problem disappears in a new chat window.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Bug Report: Approval dialog not visible after command timeout
3

Hey, thanks for the report. I see that Python commands are being rejected automatically. This could be related to the Terminal Command Execution setting or the allowlist.

Can you check and share a few details:

  1. Agent > Terminal Command Execution settings: Which mode is selected? (Auto-Run / Ask Every Time / Allowlist)

  2. If it’s set to Allowlist: Check Cursor Settings > Agents > Terminal Command Allowlist. python might not be on the allowed commands list.

  3. Do other commands work? For example ls, echo, npm, or are only Python commands being rejected?

If it’s the allowlist issue, add python there. If the settings look fine, send this info and we can dig deeper.

4

Hey Dean,

Agent > Auto-Run Mode → Ask Every Time
The problem is NOT that commands are rejected (the screenshot is not clear on that point).
The problem is actually that the confirmation window for terminal commands disappears.
Then I can’t confirm terminal commands, and the chat is stuck waiting for my approval.

Additional information:

  • If I use the “duplicate chat” feature, the problem is not present in the newly duplicated chat. (This is a workaround)
  • This issue is quite new in Cursor, I have used cursor for > 1 year, and this appeared a couple of weeks ago
1 Like
5

Thanks for clarifying. Now it’s clear the issue is that the confirmation popup disappears, not that the commands are being rejected.

This is an interesting bug. A similar issue (with parallel tool calls) was fixed in November, but based on your description, this looks like something new or a regression.

To help narrow it down, could you help with a couple things?

  1. Exact trigger: What exactly makes the popup disappear? You mentioned “type another message”. Is that the only way? Or does it disappear on its own after some time? Does clicking outside the popup also trigger it?

  2. DevTools Console: When it disappears, can you open DevTools (Help > Toggle Developer Tools) and share a screenshot of the Console tab? There might be relevant errors.

  3. Frequency: Does this happen every time you try to run a command, or only sometimes?

Your workaround with duplicating the chat is a good way to avoid losing context, thanks for sharing.

6

I am running into the same problem on Sequoia 15.7.3 after updating the latest cursor (Version: 2.3.41) from a previous version.

I also have cursor configured to “ask every time”

Command windows become hidden, and no option to confirm them.
Restarting Cursor will show previously hidden command windows, but commands will not run in that chat.

Other notes:

  • Starting a new chat solves the problem. I don’t see a “duplicate current chat option” in my IDE.

I’ll see if I can get console errors next time it happens.