Terminal WSL issue in Cursor 1.5.0

Support Bug Reports
1

I can still reproduce this happening on 1.4.6, on Windows – the description is still the same as OP and the same behaviour I’ve always seen with Cursor on Windows, utilizing a WSL workspace. After starting a session, commands will sometimes execute correctly, but frequently just hang indefinitely despite them having completed (whether successfully or failed). If I intervene, sometimes it will look at the output and most of the time it will just see that the command cancelled and then try something else, completely ignoring the output. If I don’t intervene and it hangs, which is most of the time, it will eventually time out and abort the agent chat.
What sort of details would help in debugging this?

Worth noting that cursor-agent in WSL seemingly works fine, but I am not able to utilize it current since it does not support the Auto model

2

@Kyrluckechuck thank you for the detailed update. We have more improvements on the version 1.5.0 that is now rolling out to Early Access users.

If you notice the issue still there as well check if there are any common cases when it hangs. e.g. on specific commands, if they are interactive or not, long or short output, or other details you notice. Sincerely appreciate your help!

1 Like
3

Hey @condor thanks for the response. I will check this out as soon as it’s actually available; the download API appears to be returning that 1.4.5 is the latest, and all download links, including 1.4.6 and 1.5.0 currently are actually returning the 1.4.5 installer executable!

1 Like
4

1.5.0 is rolling out as Early Access only for the moment. Once we get feedback from users we will roll it out to all users.

5

Yeah, I’m in the program but it still wasn’t rolling out; it seems the URLs for Windows are generating/reporting wrong, which can be seen on scrapers such as https://www.downloadcursor.app/ or GitHub - oslook/cursor-ai-downloads: All Cursor AI's official download links for both the latest and older versions, making it easy for you to update, downgrade, and choose any version. 🚀 – I was able to infer from the “successful” URIs released for the mac/linux versions and then swap the version on the windows link – will give it a test!
1.5.0 Windows User build for those curious

6

Its not the URLs necessarily. We are never rolling out to all users at same time. First to a few thousand users and then ramping up. So the same URL would not yet have the version for all.

7

Hmm, the URL includes the actual version number in the file name, specifically for the Windows builds, but I won’t argue there.

Unfortunately after some brief successful testing I can say I am already seeing it getting hung up on some commands again – example of a command that it got hung up on was a docker compose exec ..

Version: 1.5.0 (user setup)
VSCode Version: 1.99.3
Commit: 2947db30cb622263bb9302d7bd2c27a52e11db60
Date: 2025-08-20T01:48:01.613Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631
8

Ah, Is your docker compose exec a long running command or does it exit fast?

I assume you run this also in WSL, righ?

9

WSL - Correct!

C:\Users\Justin>wsl --version
WSL version: 2.5.10.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.66
MSRDC version: 1.2.6074
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.5768

Long running – no! This is actually near-instant, it’s executing a quick postgres lookup in that example case

docker compose exec postgres psql -U username -d database_name-c "DELETE FROM table1; DELETE FROM table2;"
11

Ok good to have the details. Sorry that your case is not yet solved but it should allow us to get closer to that goal.

1 Like
12

@Kyrluckechuck could you please share a Request ID where this issue occurs, preferably with privacy disabled so we can look into the details.

1 Like
13

Took a little bit after updating to 1.5.1 today, but fresh chat showing this with f2f40d96-0b81-4055-ae20-6480bbbb34f1 – it hasn’t fully timed out yet but the second-last command stuck for ~10+ minutes so I hit cancel and then it tried it again and currently letting it run until it times out, but it was near instant actually completing, it just can’t get the shell content for some reason it seems

15

Thank you, forwarded it to the team and they will have a look.

2 Likes
16

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.

17

This issue has been resolved in 1.6. Please update to latest stable from today on as it is rolling out to all users.

Please let us know if this specific WSL issue still persists in 1.6 in a new bug report.