Describe the Bug
On Windows 10 using a local WSL2 whenever Cursor starts a task, e.g. “cd /home/root/ddev/application && ddev exec ls -la /var/www/html”.
Cursor does not detect the task ended and the “wheel” next to “shift skip” keeps on spinning indefinitely.
Steps to Reproduce
Cursor does not detect the end of a task it executes, while you can see in the terminal in Cursor that the command has finished.
This started happening around beginning of August 2025, after a Cursor upgrade.
Expected Behavior
Cursor should detect end of the task in tasks it executes on WSL2.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.4.2 (user setup)
VSCode Version: 1.99.3
Commit: 07aa3b4519da4feab4761c58da3eeedd253a1670
Date: 2025-08-06T19:23:39.081Z
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
Additional Information
Workaround 1: copy the text from the Terminal and it to chat with “Output is:”, and then Cursor continues. But it’s a PITA to do.
Workaround 2: Put in chat “always use is_background_False”, and it works again. This is a workaround from another thread on the same issue.
Does this stop you from using Cursor
No - Cursor works, but with this issue