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).
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.
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.
