Windows - Dotnet - Shell Commands not working

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since the new Terminal was introduced ( not the legacy mode ) cursor agent is not capable to properly run commands in the terminal. It tries to run something from the temp folder and crashes with this error:
AppData\Local\Temp\ps-script-fa8bef8e-655c-4d49-819a-cdea7b85f43c.ps1:119 char:134

  • … coding]::UTF8.GetString([System.Convert]::FromBase64String(‘’{1}‘’))) …
  •                                                              ~

Missing ‘)’ in method call.

Steps to Reproduce

Let cursor agent run dotnet test

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.54 (user setup)
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

I’m having the same exact problem… Cursor is simply trying to move files into a different folder using a generate PowerShell code and failed with the same “Missing ‘)’ in method call” error.

Run Cursor as admin doesn’t solve the problem either.

4

Hey, thanks for the report. This is a known issue with the new terminal implementation on Windows when it tries to run PowerShell scripts from the temp folder.

Try this:

  1. Open Cursor Settings Ctrl+Shift+J
  2. Go to the Chat tab
  3. Find “Legacy Terminal Tool” under Inline Editing & Terminal
  4. Enable “Legacy Terminal Tool”
  5. Press Ctrl+Shift+P → “Terminal: Kill All Terminals”
  6. Fully restart Cursor
  7. Test agent commands again

This should restore proper agent command behavior. Let me know if this resolves the issue.

1 Like
5

Hi, can you run ls env: in a Powershell Terminal and post it here? Feel free to censor the output or if you’d prefer, can you send it into support and mention they should forward it to Ani

6

Hi Ani, thank you for your follow-up message.

I sent an email to Cursor support with the result of running “ls env:”. I hope it helps solving this issue.

7

Hi running in Legacy mode is also not working properly. Basically after the command runs ( successfully ) cursor agents don’t do anything, like they can’t see that powershell is done