Hey, thanks for the report. This is a known issue with the agent terminal on Windows. The sandbox and the PowerShell wrapper conflict, especially after recent updates.
Try this temporary workaround:
- Open Cursor settings
Ctrl+Shift+J - Go to Agents and turn off Auto-run in Sandbox
- In the same section, turn on Legacy Terminal Tool
Ctrl+Shift+Pthen Terminal: Kill All Terminals- Fully restart Cursor
- Try running your
psqlrequests again
Legacy Terminal Tool bypasses the new wrapper script that causes the issue. Commands will ask for confirmation before running, but they should work normally, including reading output.
Related reports and workarounds:
- Cannot run any commands due to sandbox on windows in 2.5
- [Agent shell broken after update - PowerShell wrapper script parsing error](https://forum.cursor.com/t/agent-shell-broken-after-update-powershell-wrapper-script-parsing error/151887)
The team is aware of the Windows sandbox issues. No timeline yet, but reports like this help with prioritization.
If the workaround doesn’t help, can you share:
- A screenshot of what happens when the agent tries to run a
psqlcommand, like an error message or empty output - Whether you have a custom PowerShell profile set up
Let me know how it goes.