Skipping command stops entire chat

Support Bug Reports
,
1

As title says, has been present since 2.5.x, still on latest early access.

Skip command - chat stops
Click stop button when waiting for command approve - command skipped and chat continues

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

1 Like
4

Hey, thanks for the report. We’ve recently had a few related bugs reported in this area (the “Skip/Stop” behavior when confirming a command).

To help the team investigate, could you share:

  1. Your Cursor version (Menu → About Cursor → Copy)
  2. A short screen recording showing both behaviors (when “Skip” stops the chat, and when “Stop” only skips the command)

As a workaround, if you need to skip a command without stopping the chat, try using the “Stop” button (it looks like it’s currently doing what “Skip” is supposed to do). Not ideal, but it should unblock you.

Let me know if this is critically blocking your work.

5

Hello, thank you for getting back to me.

  1. 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
  1. screenshots:
  • when skipped (i clicked on first skip only and second command got cancelled too and chat stopped)
    image
    image431Ă—340 7.72 KB
  • when clicked stop button (clicked on first, chat continued and waited for second command action)
    image
    image436Ă—348 9.3 KB

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. :slightly_frowning_face:
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.

7

Thanks for the details and screenshots.

Try updating to version 2.6. There were a few fixes in 2.6 compared to 2.5.x around confirming terminal commands. Let me know if the issue still happens after updating.