Hey, thanks for the report. This is a known issue. Sandbox on Windows doesn’t work well with custom PowerShell profiles and some other shells. Sandbox starts PowerShell in Restricted Language Mode, which blocks dot-sourcing profiles and access to temp files.
Workaround: turn off Auto-run in Sandbox.
- Cursor Settings (gear icon in the top-right, or
Ctrl+Shift+J) > Agents > Auto-run: turn it off
Or enable Legacy Terminal Tool.
- Cursor Settings > Agents > Legacy Terminal Tool: turn it on
Commands will ask for confirmation, but they won’t have sandbox restrictions. This should also help in multi-root workspaces.
Related thread with the same workaround: Git Bash Fails in Cursor Shell Tool on Windows Due to Sandbox Restrictions
The team is aware of the Windows sandbox issues. There’s no exact ETA for a fix yet, but your report helps us prioritize. Let me know if the workaround doesn’t help.