Describe the Bug
The run_terminal_cmd tool has stopped functioning during an active session. All commands fail with no output, while other tools (list_dir, read_file) continue to work normally. The tool correctly identifies the working directory but fails to execute any commands, regardless of complexity (even simple commands like ‘pwd’ fail).
Every command attempt results in:
Exit code: 1
Command output:
Command failed to run.
The previous shell command ended…
Steps to Reproduce
- Use run_terminal_cmd tool with any command (even simple ones like ‘pwd’)
- Observe that all commands fail with exit code 1
- Note that no command output is produced
- Verify that other tools (list_dir, read_file) work normally
- Observe that working directory is correctly reported but execution fails
Expected Behavior
Commands should execute successfully and produce output. The shell session should be maintained between commands, allowing for sequential command execution.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.1.0
Additional Information
- Issue appeared during an active session
- Previously working commands started failing consistently
- Other tools in the same session continue to function normally
- Shell session information appears correct but execution fails
Does this stop you from using Cursor
No - Cursor works, but with this issue