CRITICAL: Cursor 2.1.50 multiple regressions - random sandbox, context loss, file corruption, save failures

Support Bug Reports
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

CRITICAL BUG: Cursor 2.1.50 Random Sandbox Terminal

SYSTEM INFO:

  • Version: Cursor 2.1.50 (2025-12-06)
  • VSCode: 1.105.1
  • OS: macOS arm64 24.6.0 (Apple Silicon)
  • Issue started: December 7, 2025

PROBLEM:
Cursor 2.1.50 randomly opens terminal sessions in sandbox mode (no network/browser access) instead of normal mode. Same project/chat produces inconsistent results.

BEHAVIOR:

  • BEFORE (until Dec 6): Always opened terminal with full access (network + browser)
  • AFTER (from Dec 7): RANDOMLY opens sandbox terminal without network/browser
  • INCONSISTENCY: Same workflow = random results (sometimes OK, sometimes sandbox)
  • DEGRADATION: Problem worsened progressively over 3 days

TECHNICAL EVIDENCE:

  • Local environment: curl https://google.com + open -a "Google Chrome" = SUCCESS
  • Cursor sandbox: curl fails, browser cannot open
  • macOS permissions verified: Full disk access ✓, Automation (Chrome, Finder, System Events) ✓, Firewall inactive ✓

CURSOR RESPONSE:
“Cannot guarantee future sessions won’t start in sandbox. Environment choice made by Cursor/IDE at terminal opening. No setting exists to force always non-sandbox.”

BUSINESS IMPACT:

  • Automated workflow broken (database project with 15,000 contacts)
  • Production environment unreliable
  • Cannot guarantee stable environment for enterprise use

REQUESTED FIX:

  1. Immediate fix for random sandbox behavior
  2. Configuration option to “Force always non-sandbox terminal”
  3. Rollback to pre-2.1.50 functionality
  4. Prevent random sandbox initialization

PRIORITY: CRITICAL - Blocks professional workflows
WORKAROUND: Use local terminal (not Cursor) for network operations

This is a regression from working functionality. Enterprise users need reliable, consistent environments.

Steps to Reproduce

Steps to Reproduce:

  1. Open Cursor 2.1.50
  2. Create new chat or continue existing project
  3. Try to execute any command requiring network access (curl, web requests, API calls)
  4. Try to launch browser automation (Chrome, Selenium, Playwright)
  5. Observe random behavior: sometimes works (non-sandbox), sometimes fails (sandbox)
  6. Close and reopen Cursor terminal → repeat steps 3-4
  7. Results vary randomly despite identical setup and commands

Expected Result:
Terminal should consistently have network and browser access (like pre-2.1.50)

Actual Result:
Random sandbox mode blocks network/browser access unpredictably

Frequency:
Intermittent - approximately 50% of sessions open in sandbox mode

Additional Notes:

  • Same project files, same commands, different results
  • No user configuration changes between working/non-working sessions
  • Local terminal (outside Cursor) always works consistently

Expected Behavior

Expected Behavior:

  1. Terminal should consistently open with full network and browser access
  2. Commands like curl https://google.com should always succeed
  3. Browser automation (open -a "Google Chrome", Selenium, Playwright) should always work
  4. Python scripts requiring network requests should execute without errors
  5. Environment should be predictable and stable across all sessions
  6. Same behavior as Cursor versions prior to 2.1.50 (always non-sandbox)
  7. No random switching between sandbox/non-sandbox modes
  8. Professional workflow tools should have reliable access to system resources

Current Broken Behavior:

  • Random sandbox mode prevents network access
  • Inconsistent environment between identical sessions
  • Unpredictable failures in production scripts
  • No user control over terminal environment type

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Current Cursor Version (Menu → About Cursor → Copy):
Version: 2.1.50
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

For AI issues: which model did you use?
N/A - This is not an AI model issue. This is a terminal/environment configuration bug in Cursor IDE that randomly opens sandbox vs non-sandbox terminals, blocking network and browser access for system scripts and automation tools.

The issue affects the underlying terminal environment that Cursor provides, not AI code generation or suggestions.

For AI issues: add Request ID with privacy disabled

For AI issues: add Request ID with privacy disabled
N/A - This is not an AI model issue. This is a terminal/environment configuration bug in Cursor IDE that randomly opens sandbox vs non-sandbox terminals, blocking network and browser access for system scripts and automation tools.

The issue affects the underlying terminal environment that Cursor provides, not AI code generation or suggestions.

Additional Information

Additional Information:

  • Bug introduced specifically in version 2.1.50 released 2025-12-06
  • Problem affects enterprise/professional workflows requiring reliable automation
  • Workaround: Use system Terminal/iTerm instead of Cursor integrated terminal
  • Impact: Database automation project with 15,000 contact records blocked
  • User has verified all macOS permissions are correct (disk access, automation, firewall)
  • Local environment tests pass consistently (curl, Chrome launch work fine)
  • Only Cursor’s integrated terminal exhibits random sandbox behavior
  • No user configuration changes made between working/broken sessions
  • Cursor staff confirmed: “Cannot guarantee future sessions won’t start in sandbox” and “No setting exists to force always non-sandbox”
  • Request priority: CRITICAL - affects production automation systems
  • Suggested fixes: Either rollback sandbox logic to pre-2.1.50 behavior OR provide user control over terminal environment type - Additional Information:
  • Bug introduced specifically in version 2.1.50 released 2025-12-06
  • Problem affects enterprise/professional workflows requiring reliable automation
  • Workaround: Use system Terminal/iTerm instead of Cursor integrated terminal
  • Impact: Database automation project with 15,000 contact records blocked
  • User has verified all macOS permissions are correct (disk access, automation, firewall)
  • Local environment tests pass consistently (curl, Chrome launch work fine)
  • Only Cursor’s integrated terminal exhibits random sandbox behavior
  • No user configuration changes made between working/broken sessions
  • Cursor staff confirmed: “Cannot guarantee future sessions won’t start in sandbox” and “No setting exists to force always non-sandbox”

ADDITIONAL REGRESSIONS IN v2.1.50:

  • Context loss: Fails to maintain conversation context between sessions
  • Unauthorized file creation: Creates files without user permission
  • Save failures: Claims to save but doesn’t actually save files
  • File corruption: Empties existing files during save operations
  • Protocol changes: Changed file writing without notification
  • Inconsistent behavior: Same commands produce different results

These compound regressions make v2.1.50 unusable for professional work. Request immediate rollback to v2.1.49 behavior.

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like
2

Hey, thanks for the report. In 2.1.50 we’ve confirmed a network bug in the execution sandbox (see the report and status: bug identified, fix in progress): Cursor stopped pushing to GitHub and lost all internet access

3

Hello!!! thank to you, too!
I hope they will solve.
Best
Massimo

1 Like
4

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