AI agent is sandboxed, cannot run tests or work with GitHub

Support Bug Reports
, , ,
3

Hey, thanks for the report.

This is a known issue on Windows in versions 2.4.21 to 2.4.27. A few users ran into the same thing. The agent runs commands, but it doesn’t get any output.

Please check the DevTools console so we can see why:

  1. Open Developer Tools (Help > Toggle Developer Tools)
  2. Run a command via the agent (anything like mvn test or git status)
  3. Copy the logs from the Console and paste them here (look for errors mentioning “path”, “ENOENT”, or “cursor-agent-exec”)

In the meantime, try these workarounds:

Workaround 1: Legacy Terminal Tool

  • Settings > Agent > Legacy Terminal Tool: turn it on
  • Restart Cursor

Workaround 2: Set an explicit shell

  • Settings > Terminal > Integrated > Default Profile: Windows
  • Pick PowerShell (not “null” or “default”)
  • Restart Cursor

Workaround 3: Check PATH
In a normal PowerShell (not inside Cursor), run:

where.exe git
where.exe mvn
$env:PATH

If git or mvn aren’t found, you’ll need to add them to PATH.

In a similar thread, one user temporarily fixed it with a PowerShell profile workaround. If you want, here’s the thread with details: Terminal problems when used by agent. The issue came back though, so it’s not a full fix.

Please share your DevTools logs and we’ll have a better idea what’s breaking.

Sandbox Network access: Blocked issue