Cursor can still not tell when a terminal command has finished!

Describe the Bug

This has been an error since day 1 - A terminal command finishes that it has run and it just sits there spinning waiting for it. Clicking Skip makes it think the command failed even though it might have succeeded.

Steps to Reproduce

GPT-5
Run terminal commands like the AWS CLI
Experience Pain

Expected Behavior

When a terminal command completes the agent should take back over!

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

0.43
On a different machine so cant get the rest

Additional Information

Wont upgrade to 0.47 until it has been thoroughly tested - cant afford to have to constantly trace back through versions to find a working on

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

4 posts were merged into an existing topic: Run Command often freezes