Hello, thank you for getting back to me.
- version:
Version: 2.5.26 (user setup)
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Early Access
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045
- screenshots:
- when skipped (i clicked on first skip only and second command got cancelled too and chat stopped)
- when clicked stop button (clicked on first, chat continued and waited for second command action)
As per your question, whether this is critically blocking my work. Yes and no. This issue specifically a little as I have to think about it every time I need to run a command and it is not possible to use this workaround in subagents and need to restart entire chat with specific instructions to prevent bad commands from being executed.
What is critically blocking my work, and please dont take this personally or as me being rude, but the entire IDE is highly unstable. I stumble on new bugs every single week. Some bugs get fixed but then return in new versions. Each new minor version I go out of my way and test functionality I use just to see what is broken. Just today WSL stopped working out of the blue, I did not even bother reporting the issue at this point and just downgraded to previous version. It has been like this for basically past 6 months, if not more. There is bugs everywhere. I do not want to tell you what to do, I do not know what is going on internally, all I know is that from consumer standpoint, I am highly disappointed as my experience using Cursor gradually decreases. 
Great example is version 2.5 release, it came out 2 weeks ago and the big thing was async subagents. It turns out this very feature itself does not work (or at least not properly). Me and other users reported it the same day on the forum, but only today we get confirmation of the bug existing - Cursor 2.5: Async Subagents - #21 by Colin.