Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
IDE shows that agents is wating for the approval, but there is not approval dialog
Steps to Reproduce
NA
Expected Behavior
If agents waits for approval, the dialog should be shown
Operating System
MacOS
Version Information
3.2.0 pre 22
Does this stop you from using Cursor
No - Cursor works, but with this issue
Hi @Eugen_Konkov
This is a known issue — the approval dialog (Run/Skip/Allowlist buttons) sometimes fails to render while the agent shows “Waiting for Approval.” Our team is actively investigating this, particularly in the Glass UI.
A couple of things to try:
-
Scroll down in the conversation — the approval card may have rendered below the visible area
-
Start a new chat session — the approval state can get stuck in long sessions
-
Enable Auto-run for trusted commands: Cursor Settings > Features > Auto-run — this lets the agent execute commands without manual approval, bypassing the issue entirely
You may also find this related thread helpful: Getting stuck waiting for approval with no ‘Approve’ button
Since you’re on a pre-release build (3.2.0 pre 22), this may also be addressed in a future update.
v3.2.0 pre 32
You can see that the first message is doubled and not Approve dialog
The underlying fix for the missing approval dialog hasn’t shipped yet, which is why you’re still seeing this on pre 32. Our team is actively working on it.
One additional workaround to try: if you have multiple agent tabs open, switch to a different agent tab and then switch back. This can sometimes force the approval UI to re-render.
Regarding the doubled first message: is this the same behavior you reported in your other thread? If so, that’s being tracked separately. If this is a different pattern, a request ID from the affected session would help us investigate (three-dot menu at the top of the chat > Copy Request ID).
3.2.0-pre.48.patch.0
This is very annoying, it seems after this agent is starting to thing from the beginning when I press “Stop” button. But I have no choice.
Please note. Here we do not have “Request ID” available.
Ok. I have small work around:
-
send new message
-
edit, send again
-
delete it
after this, after 5 -10 sec timeout agent started to think.