Cursor never completes request

Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I can not get Cursor to complete 1 task…it starts and then just sits and spins forever! Or it opens 6 terminals and sits and spins forever!

Steps to Reproduce

Go into project, ask Cursor to perform any task…watch it do nothing and sit and spin forever!

Expected Behavior

Read request, plan execution, finish solution, wait for next request.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.26
VSCode Version: 1.99.3

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. Does it get stuck while running commands in the terminal? Could you also let me know if this happens in a new chat? Also, which model are you using?

3

Yes it happens with fresh chat windows, I’ve tried literally everything I can think of including restarting Cursor and rebooting my machine. I was on Auto…I just tried Gpt-5 and I get the same result it just hangs.

2 Likes
4

Terminal Commands hang for me, often.
Cursor seems unable to read the output.
Sometimes it thinks a command has failed when it hasnt, other times it just stalls completely and fails to either execute or read it.

I have had these issues for a long time.
I frequently have to restart terminals, or ask cursor to redo the work.
Sometimes it seems like the only way to get it to work is to restart cursor completely.

Sometimes it happens with sonnet 4.0 aswell.

It can happen in a new chat and old ones.

Another similar type of issue is sometimes:
that I have to click enter twice in short succession inside the terminal to “kickstart” the AI-model. This works 70% of the time, but when writing a prompt I can be 90-95% sure that that cursor will fail to automatically complete the prompt due to these errors.

Other thread explaining these issues: Run Command often freezes - #163 by b3nw

1 Like
5

This far, 1.6.26 has not done that even once in my Windows when I switched powershell to legacy CMD terminal. It even survives timeout command, where it wants to wait for 10 seconds for runtime to finish. And it is super easy to test in a project, just create .vscode\settings.json and paste this there:

{
    "terminal.integrated.defaultProfile.windows": "Command Prompt",
    "terminal.integrated.profiles.windows": {
        "Command Prompt": {
            "path": "C:\\Windows\\System32\\cmd.exe",
            "args": []
        }
    }
}

Then restart Cursor and start new chat. Ask agent to do “dir” or something to make sure it is now using cmd. Then enjoy. And if you want to go back, then delete those lines.

1 Like