Bug - Stuck Terminal Commands

Describe the Bug

The agents often get stuck when running commands, even when the command completes successfully. This creates a problem where we have to sometimes shift to terminal, shift+skip or send a new command which cancels the command. This sends the incorrect context to the agent. PLEASE give us a button or function to help the agent move forward when stuck waiting on the command like, ‘command completed’ or something. Thank you.

Steps to Reproduce

Just run enough commands in Cursor and it will happen. I am running Windows 11 on a laptop.

Expected Behavior

What should happen is that after the command is finished running, the agent moves on, but it often does not.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.7 (user setup)
VSCode Version: 1.99.3
Commit: 5d56108ff2401c28f239aa2a527ef424ce7719a0
Date: 2025-07-31T04:16:31.276Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

hi @maverick-software and thank you for your bug report.

We have launched several bug fix updates and are currently at version 1.3.9, could you update to the latest version to see if your issue is resolved?

We are tracking a few reports with Windows PowerShell issues in Cursor to see if this is still occurring.

1 Like

A post was merged into an existing topic: Run Command often freezes