Missing skip and open in command output, process hangs

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When running commands with bash in Cursor (e.g., ls -la), the output does not show the usual skip and open options. The result is partially displayed, but the process hangs indefinitely at this point. It feels like the command execution never finishes, leaving the panel stuck.

Steps to Reproduce

  1. Open Cursor.

  2. Run ls -la (or any shell command) in the command line panel.

  3. Observe the output area.

Expected Behavior

  1. The command should execute and complete normally.
  2. The output should include actionable buttons:
    • Skip – to ignore or skip irrelevant output.
    • Open – to directly open files or directories listed in the output.

Screenshots / Screen Recordings

7723268b-bf2d-48bb-b40c-da911f495e0b.png
7723268b-bf2d-48bb-b40c-da911f495e0b.png1032×227 13.6 KB

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

版本: 1.6.27
提交: 1.99.3
日期: d750e54bba5cffada6d7b3d18e5688ba5e944ad0
Electron: 2025-09-17T20:21:17.042Z
ElectronBuildId: 34.5.8
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.1
OS: 13.2.152.41-electron.0

For AI issues: which model did you use?

Auto

Additional Information

  • Output is not displayed, and no skip or open options appear.

  • The command process hangs and never terminates, leaving the panel stuck until manually interrupted.

This bug breaks the workflow in two ways:

  • Users cannot interact with the output (no quick open/skip).

  • Every command execution hangs, forcing a manual reset and significantly slowing down development.

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. We’ll look into it.

3

Can you reveal how you determine if a command has ended?

Are you now training a local model to determine whether to end based on the most recent string from the terminal?

Or is it that the terminal tells you some information, but sometimes it doesn’t, leading to persistent problems that haven’t been fixed?

After all, this issue has been around for a long time, even the simplest git commands might trigger this problem.