Missing approval buttons in Cursor IDE prevent command execution

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

the approval buttons for launching PowerShell commands are no longer displayed. It is impossible to proceed. The agent remains pending approval, but it is impossible to validate.

Steps to Reproduce

from each request

Operating System

Windows 10/11

Version Information

Version: 2.6.14 (user setup)
VSCode Version: 1.105.1
Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080
Date: 2026-03-08T15:36:54.709Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

GTPT-5.4 and Kimi k2

Additional Information

Honestly, team, I don’t often post on the forum, but every update brings new bugs, and these are very serious bugs that prevent us from working.

Does this stop you from using Cursor

Yes - Cursor is unusable

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When an Agent wants to execute a command that requires approval, there used to be UI affordances showing the requested command and options to approve/reject. Since the latest update, there is now only a “Waiting for Approval…” status line above the chat input box, but no affordance for actually signalling approval.

I can reject a request by entering anything in the chat area. But approval is off the table. This bug makes Agents fundamentally incapable of any action that has not been preapproved.

Steps to Reproduce

Ask the agent to perform a command that would require approval, such a curl command to pull the content from any remote URL.

Expected Behavior

I expect to see an expandable box describing the requested command, which, when expanded shows the command, along with buttons to approve/reject and so on.

Operating System

Linux

Version Information

Version: 2.6.22
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
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: Linux x64 6.8.0-106-generic

Additional Information

The Agent session was started on a previous version. I had been ignoring the upgrade notification, but then Cursor crashed, and so I was force-upgraded.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

@Fabz @jimbojw Thanks for the reports!

We have an open bug ticket to address this. Some users have reported that downgrading to v2.5 fixes the issue.