Cursor v1.2 - Release Discussions

[engels74]

Hey team,

I’ve created a detailed thread here:

Cursor Agent commands fail to execute or detect completion

Describe the Bug When using Cursor Agent with WSL, commands either fail to execute entirely or complete successfully but the Agent doesn’t detect completion, requiring manual intervention. Two specific issues occur: Commands don’t run at all - Agent gets stuck with no terminal started. Only solution is “Move to background” as Skip button is unresponsive. Commands run but Agent doesn’t detect completion - Commands execute successfully but Agent waits indefinitely, requiring manual “Skip” butto…

Issue persists in Cursor v1.2.0:
The update did not resolve the problem with the Agent not detecting command completion.

Example:

Developer Console Logs:
https://logs.notifiarr.com/?652358986dc67d98#66sEwr8HjUVHh9dXd13nXA2nj869daugtmWAZNiZwE55

Request-ID: d2c80cea-ef9d-47c5-8f26-f9b072b50771

Cursor Version:

Version: 1.2.0 (user setup)
VSCode Version: 1.99.3
Commit: eb5fa4768da0747b79dc34f0b79ab20dbf582020
Date: 2025-07-01T20:01:14.203Z
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

WSL Version:

WSL version: 2.5.7.0
Kernel version: 6.6.87.1-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.26100.4351

Bash version:

GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)