‘Allow’ Button Requires Multiple Clicks

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I need to click multiple times on the allow button for the sub-agent to proceed. I understand this has been addressed as a bug but I still witness this behavior(occasionally).

Steps to Reproduce

I think this happens when the sub-agent needs permission to perform multiple operations. They get bundled together but the Cursor requires the user to click “Allow” for each permission. At least that is my guess. However like I said they are bundled together and if that is the case it’s not clear for the user.

Also if you look at the screenshot why does it say “Run Run Soql…” whys “Run” mentioned twice?

Expected Behavior

To only click “Allow” once.

Screenshots / Screen Recordings

Screenshot 2026-06-03 at 12.29.04 PM.png
Screenshot 2026-06-03 at 12.29.04 PM.png1312×132 13.1 KB

Operating System

MacOS

Version Information

Version: 3.6.31
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
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
xterm.js: 6.1.0-beta.220
OS: Darwin arm64 24.5.0

For AI issues: which model did you use?

Composer 2.5 Fast

For AI issues: add Request ID with privacy disabled

copy request-id not working

Does this stop you from using Cursor

No - Cursor works, but with this issue

8

Hi @Nikolay_Kolev Thank you very much for raising these issues. I’ve reproduced both of them - the allow button being unclear how many times you need to press to Allow Subagent actions as well as the typo with the Run Run. I’ve raised bug reports for each of these. We’ll let you know any updates!

In the mean time, the best semi-workaround for the allow button is to go into the subagent and look to see the approval that is needed. You can return back to the main agent if you would like, but the subagent is a good place to see the actual behavior being requested. I agree we should make this more clear and transparent. Thank you!