Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Hi, I don’t know what happened but today the agent has not been able to capture stdout/stderr from my WSL2 environment:
Commands are running, but stdout isn’t being captured. Verifying the script exists and trying a different approach:
Stdout isn’t being captured: commands run, but only the command text appears in the output, not the stdout. Exit code -1 suggests an issue. Cleaning up the test file:
Test result: stdout capture isn’t working.
Commands execute (visible in output)
Exit code: -1
Stdout from commands isn’t captured (only the command text appears)
This suggests an issue with stdout capture in this environment. The terminal tool runs commands but doesn’t return their stdout/stderr output.
Steps to Reproduce
I am using WSL2 and it’s not capturing stdout/stderr
Expected Behavior
Usually it captures output and error when running commands
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.46 (user setup)
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
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.26100
Does this stop you from using Cursor
No - Cursor works, but with this issue