Cursor getting stuck in terminal

Bug Reports
54

Cursor getting stuck in terminal is very consistent in Windows WSL or PowerShell. The command finished and return to the shell prompt waiting for input but cursor just can’t detect that and sit there. On MacOS it rarely happens.

When it’s stuck, you can always get it unstuck by click on the shell terminal and press enter a few times.

56

@jchip which version are you on now? 1.3.3 (Beta) has launched an update for this.

57

@condor

Version: 1.3.3 (user setup)
VSCode Version: 1.99.3
Commit: e589175333a2d938c3d944f9bf0993155e655e70
Date: 2025-07-26T19:28:32.726Z (20 hrs ago)
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

58

I have the same issue too. I noticed that this does not happen immediately when I start a new chat session. However, after some point (maybe in next terminal command, maybe later) it will start getting stuck. Claude Sonnet 4 noticed this issue by itself ( and checked if there is an issue with running terminal commands by running pwd and this command didn’t finish running.

Version: 1.2.2 (user setup)
VSCode Version: 1.99.3
Commit: faa03b17cce93e8a80b7d62d57f5eda6bb6ab9f0
Date: 2025-07-07T06:19:13.016Z
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.19045

59

@Erkan_Arslan we are working on a solution for Cursor 1.3 which should fix the issue you have. Others proposed various solutions for 1.2.4.

60

@jchip thanks for the details, updated dev team.

61

This and the “q is not a command” issue have been around for a while now, when is a fix going to be released?

62

@mhallenbeck we are working on this right now with v1.3.4

63

Isn’t 1.3.4 released? In my help->about it says version 1.3.4

1 Like
64

Yes, you are having the same issue still on 1.3.4?

1 Like
65

Hey, can you confirm if the issue persists in new chats as well?

2 Likes
66

Sure! Lemme spin it up and check

2 Likes
67

Yeah, this issue is now worse than ever. The AI can’t seem to figure out how to use the consoles at all for me. It constantly requires babysitting and frequently needs me to press Ctrl+C or manually exit the terminal. By that point, the AI—for some reason—can no longer see the terminal I just pressed Ctrl+C on, forcing it to start all over again and burn through hundreds of tokens repeatedly, often doing who knows what, since the terminal is usually in this tiny, unopenable, compressed view.

I’d say that out of 10 terminal usages, it successfully uses the terminal correctly only 4 times. In the other cases, it abandons the process, leaving my Legion Pro bogged down by 50+ terminals it never closed. And I can’t close them without shutting down the whole app, lol.

Edit to clarify os
This happens on windows, ubuntu 22.04, and ubuntu 25

4 Likes
68

Same issue here on 1.3.4 with WSL Ubuntu 22.04
Working with WSL is basically impossible

1 Like
70

Hey, thanks for the report. We’ve released a new update, version 1.3.5, which should fix this issue. Try updating.

5 Likes
71
1 Like
72

Hey! After updating to 1.3.5 and doing some very basic testing it looks like it’s working well! :grin:

3 Likes
73

Works like a charm, thanks a lot :folded_hands:

3 Likes
74

I still get intermediate hangs but it’s a lot better now, and I don’t get any of the “q command” errors. I feel like when it tries to run a command that requires input (like git diff), after you kill it it’s slower/hangs on other commands, but I have no proof of that yet.

1 Like
75

Hi,
I’m using WSL (Arch) with fish, and terminal commands from the agent hang everytime. I tried changing fish’s config files as described above but it doesn’t help the issue. Here are my version details, thanks in advance !

Version: 1.3.6 (user setup)
VSCode Version: 1.99.3
Commit: 68b8fe7396ea37d8acdaaaa08ba316ba359a4160
Date: 2025-07-30T18:17:09.810Z
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

1 Like