AI shell now sandboxed, can’t run real git/PowerShell?

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In Cursor, the AI used to be able to run all my PowerShell + git commands for me (add/commit/push, etc.).
Now it looks like the shell is fully sandboxed:
git status, git push, Get-Location run in an isolated environment, not in my real local clone.
The AI can edit code, but can’t copy image files on my disk or push to my actual GitHub remote.
Is this the expected behavior now?
Is there any supported way to let the AI execute real git/PowerShell commands on my machine (opt‑in), or is the intended workflow that the AI only edits code and I always run git/PowerShell manually?

Steps to Reproduce

try to ask cursor to make a git push by it self

Operating System

Windows 10/11

Version Information

Version: 2.5.26 (system setup)
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi there!

This is expected. Cursor now runs Agent terminal commands in a sandbox by default. The sandbox creates a restricted environment that can block access to your credentials, SSH keys, and tools outside the workspace. This is a known Windows limitation that the team is working on.

To get your git/PowerShell commands working again:

  1. Change Auto-Run mode: Cursor Settings (gear icon or Ctrl+Shift+J) > Agents > Auto-Run > switch to “Ask Every Time”. Commands will prompt for confirmation but run in your real shell with full access.

  2. Enable Legacy Terminal Tool: Cursor Settings > Agents > toggle on Legacy Terminal Tool, then restart Cursor.

  3. Set an explicit default shell: Press Ctrl+,, search for terminal.integrated.defaultProfile.windows, and select “PowerShell” or “Command Prompt” explicitly (don’t leave it as default/null). Restart Cursor.

Try these in order – most users are unblocked after step 1 or 2.

Let us know if you’re still stuck after trying these.

Best,
Mohit

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.