Run confirmation replaces Run with Cancel immediately, causing accidental cancellations

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After clicking Run on the command confirmation prompt, the UI immediately swaps the button to Cancel in the same location. It’s easy to accidentally click Cancel right away, which interrupts the process and can leave it in a broken/partial state.

Steps to Reproduce

  • Trigger a command that shows the Run confirmation dialog.
  • Click Run.
  • The button instantly becomes Cancel in the same spot; a quick second click cancels the run.

Expected Behavior

After clicking Run, the UI should prevent accidental cancel (e.g., no immediate button swap in the same spot, delay, or require a separate action to cancel).

Operating System

MacOS

Version Information

Version: 2.4.28
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. This is a known UX issue: when you click Run, the Cancel button shows up in the exact same spot, so it’s easy to accidentally cancel with a double-click.

As a temporary workaround, you can enable auto-run for terminal commands (Cursor Settings > Agents > Auto-Run) if that works for you. Then the confirmation prompt won’t show up at all.

4

Yea I know that, but in many cases there are commands that I specifically ask it to confirm with me before moving forward, specially in plan mode, using different models. So other then refactoring it… I would probably suggest adding a small, like milliseconds delay? Before the cancel appears. That to me is like the quickest fix and will do the job until you figure out how to improve the UI. Let me know what you think.

P.S. Thanks for the quick response.

5

Agreed, a millisecond delay sounds like a reasonable solution. I’ll pass your feedback to the team.

6

@deanrie thank you guys for fixing the ui on this. It’s perfect now. :victory_hand: