Regression: CLI commands spawned by Cursor agent freeze indefinitely

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I asked Cursor to run claude CI command:

Ran:

claude --agent test-runner -p "Run these tests: Integrations/VoiceCall/DrachtioBridge"

It’s still running after about 2 minutes and the terminal log doesn’t show any stdout/stderr yet—only that the process started. So either the agent is slow to start or its output isn’t being captured there.

Check the terminal where it’s running for live output. If it stays blank or never finishes, that may match the “cli agents freeze” behavior in .notes/cliAgentsFreezeInCursorReport.md.

Nothing happens, after a while separate shell is spawned with this command:

Interesting observation: I have detailed logs from this Claude subprocess, bt they only start to run *after I manually terminate this terminal Window Cursor spawned.

Steps to Reproduce

Run this example Claude Code headless command:

claude --agent test-runner -p "Run these tests: Integrations/VoiceCall/DrachtioBridge"

Request ID:
d2fd302a-8761-454f-9a06-a5f4b1049caa

Expected Behavior

Shell subprocess spawns and completes, returning success. Or even error - but not hang indefinitely.

When I run same command manually, I get some output (even though approvals are not configured with this setup in mind).:

$ claude --agent test-runner -p "Run these tests: Integrations/VoiceCall/DrachtioBridge"
I need approval to run the test command. This is a security measure in your environment. The command I'm attempting to run is:

Operating System

Windows 10/11

Version Information

Version: 2.6.11 (user setup)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

This was introduced around February, this setup used to work for me for few months then.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, thanks for the report. This is a known issue: the agent’s terminal commands hang and don’t return stdout or stderr. We’ve seen a few similar reports over the last month on different OSes.

Try enabling Legacy Terminal as a temporary workaround:

  • Settings > Cursor Settings > Agents > Legacy Terminal: enable it
  • Restart Cursor
  • Try again

Also, can you share a couple details:

  • Which shell is Cursor using? (PowerShell, CMD, Git Bash, WSL?)
  • If Legacy Terminal doesn’t help, please send the console logs: Ctrl + Shift + P > Developer: Toggle Developer Tools > Console tab

The team is aware of the issue. No specific ETA yet, but your report helps with prioritization.

Let me know how it goes.

4

It should be using git bash.

Now that I toggled “legacy terminal” on Cursor gets “this operation requires elevated privileges” for every command and is effectively unusable.

BTW I don’t see any “sandbox” options in Cursor again. Could you please stop pushing breaking changes to Cursor setup every week without notice?

5

Thanks for the info, and sorry that the workaround caused a new issue. Git Bash plus Legacy Terminal on Windows is a known pain point.

A couple things you can try:

  • Turn Legacy Terminal off again, and instead try temporarily switching your shell to PowerShell: Ctrl+Shift+P > Terminal: Select Default Profile > PowerShell. Then restart Cursor. This can avoid MSYS2 and sandbox issues.

The team is aware of the terminal freeze issue. There’s no exact timeline yet, but every report helps with prioritization. Let me know how it goes with PowerShell.