Remote shell execution failed

[Dina]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor shell execution bug - Shell commands execute but return no output in Cursor worktree environment

Steps to Reproduce

Reproduction Steps
Step 1: Open Cursor with worktree workspace

1. Open Cursor IDE2. Connect to remote host via SSH3. Open workspace located at: /home/quant/.cursor/worktrees/polymountian__Workspace_/cll
   Step 2: Execute a simple command
   Command: ls -laExpected: Directory listing with files and permissionsActual: Exit code: -1, empty output
   Step 3: Execute a Python command
   Command: python --versionExpected: Python version string (e.g., “Python 3.10.5”)Actual: Exit code: -1, empty output
   Step 4: Execute a command with output redirection
   Command: echo “test” > /tmp/test_output.txt && cat /tmp/test_output.txtExpected: File created and contents displayedActual: Exit code: -1, empty output, cannot verify if file was created
   Step 5: Execute a background process
   Command: python script.py &Expected: Process starts in background, PID returnedActual: ERROR: spawn /usr/bin/bash ENOENT
   Step 6: Check terminal logs
   Location: /home/quant/.cursor/projects/…/terminals/*.txtObservation: Commands show “duration: 0ms” indicating they’re queued but not executing

Expected Behavior

Expected Behavior
Commands execute normally
Output is returned to the tool
Exit codes reflect actual results (0 for success, non-zero for failure)
Background processes spawn correctly
File operations are visible (e.g., chmod +x changes permissions)

Operating System

Windows 11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.50 (user setup)
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: Windows_NT x64 10.0.22621

Additional Information

Things keep changing in these updates. I use to not have any issue with cursor reading and existing shell execution commands. The change log hasn’t been updated since November and I know have had 2 updates since than.

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. This is a known regression in the terminal infrastructure that we’re tracking here: Agent Terminal not working

For SSH Remote, it may be related to your shell configuration. Please check:

• Which SSH extension are you using (Microsoft Remote-SSH or Anysphere Remote SSH)?
• Do you have custom config in .bashrc, .bash_profile, or an exec zsh on the remote machine? (see fix: AI Terminal over SSH fails with `dump_bash_state: command not found` and random "command not found" lines)
• Try launching Cursor with --disable-extensions and see if the issue reproduces

Logs from Help → Toggle Developer Tools (Console) during the command attempt are also helpful.

[Dina]

Hey!

Looks like I just delete my workspace storage settings from the past few days and it works again. not sure why it broke though.

[Dina]

Scratch that, it worked for a few minutes and it stopped working again.

[Dina]

restarted workspace and it works again… lets see if it stops workign again

[Dina]

okay, it broke again.