Sandboxed shell commands return no exit status

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

while working with Fabel in Cursor, your system asked me to report the problem/issue: “sandboxed shell commands return no exit status on Windows” /no output; same commands work only when run with elevated/all permissions My Version: 3.7.42 (user setup)
VS Code Extension API: 1.105.1
Commit: 5702c9cfca656d8710fad58402fe37f14345e3a0
Date: 2026-06-15T19:39:42.738Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Steps to Reproduce

Cursor /Fabel is helping me to edit several word files for journal submission

Expected Behavior

I dont know exactly, the errors were reported by your system, which asked me to report the issue to you

Operating System

Windows 10/11

Version Information

Version: 3.7.42 (user setup)
VS Code Extension API: 1.105.1
Commit: 5702c9cfca656d8710fad58402fe37f14345e3a0
Date: 2026-06-15T19:39:42.738Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Fabel

Additional Information

sandboxed shell commands return no exit status on Windows

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the report. This is a known Windows issue. In older builds, you could enable Auto-Run in Sandbox, but on Windows the sandbox mode for shell commands isn’t supported, so commands returned no exit status with no output. In newer versions, this option is hidden on Windows, and the issue is already fixed.

You’re currently on version 3.7.42 build from June 15, which is pretty outdated. What to do:

  1. Update Cursor to the latest stable. This is the main fix. Go to Help > Check for Updates, or reinstall from Cursor · Download.
  2. Immediate workaround if you can’t update yet. Open Settings > Agents > Auto-Run and switch Auto-Run in Sandbox to Use Allowlist. Alternatively, enable Legacy Terminal Tool. Either option avoids the broken sandbox path on Windows.

After updating, commands should run normally without elevated permissions. Let me know if the issue still happens after the update.