Cursor Agent commands fail to execute or detect completion

Bug Reports
1

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:

  1. Commands don’t run at all - Agent gets stuck with no terminal started. Only solution is “Move to background” as Skip button is unresponsive.
  2. Commands run but Agent doesn’t detect completion - Commands execute successfully but Agent waits indefinitely, requiring manual “Skip” button press every time.

Steps to Reproduce

  1. Use Cursor v1.1.3 on Windows 11 with WSL setup
  2. Install and use Anysphere WSL extension
  3. Run any Agent command (example: cd /home/dev/GitHub/engels74/tgraph-bot-source && uvx basedpyright tests/test_data_fetcher.py)
  4. Observe either:
    • Command never starts execution
    • Command runs but Agent never detects completion

Expected Behavior

  • Agent commands should execute immediately when triggered
  • Agent should automatically detect when commands complete and proceed to next steps
  • No manual intervention should be required

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.3 (user setup)
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:55:04.603Z
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

Additional Information

Visual Examples:

Console Logs:

  • Run #1 (Request ID: a2fd5210-09f5-4a03-899f-cc7c07373ab2): PrivateBin
  • Run #2 (Request ID: 32feb853-8fda-453a-ace6-76e2f9e63238): PrivateBin

Configuration:
Using Anysphere WSL extension for WSL integration

Operation System Info

  • OS: Windows 11 Pro (24H2, v26100.4351)
  • WSL Version: 2.5.7.0
  • Kernel: 6.6.87.1-1
  • Terminal: GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)

Does this stop you from using Cursor

No - Cursor works, but with this issue

4 Likes
3

Hey, we believe we might have some improvements to terminal command detection coming in our next release that should resolve this!

Once v1.2 is out, do let me know if you are still seeing this issue!

2 Likes
4

Hey danperks,

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

Example:
7bxYR5Hvz
Developer Console Logs:

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

5

I’m currently rate-limited, but from earlier testing, v1.2.1 did still not solve the issue.

Here’s to hoping a later 1.2.x version will fix it :slight_smile:

1 Like
6

I ended up requesting a refund for reasons listed here.

I won’t be updating this thread any longer

The issue is still not fixed as of this date, it’s odd that it’s marked as solved as of v1.2.X while it clearly is not solved. I tried supplying all the information needed in the original thread, and also tried via email (never got an answer).

Hopefully it’ll be solved in the future.

Good luck to everyone still using Cursor!