Cannot see or approve agent requested commands requiring approval

[jimbojw]

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

[deanrie]

Hey, this is a known issue. The approval buttons Run, Skip, Allowlist sometimes don’t render even though the agent shows Waiting for Approval. It reproduces across different OSes and versions.

Starting the session on an older version and then Cursor updating after a crash likely made it worse. A stale session state can trigger this bug.

Workaround: stop the agent and start a new chat. The buttons usually come back.

Main discussion thread: I am not able to approve command. Interface bug

The team is aware of the issue. There’s no ETA yet, but your report helps with prioritization, especially since it confirms the bug on 2.6.22 and Linux.

Let me know if the workaround doesn’t help.