Cursor version 2.1.39 has terminal bug

[Riaan_De_Winnaar]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The terminal tool in Agent mode fails to properly capture and display stderr (standard error) output. When commands produce error output to stderr, it is not being captured or displayed correctly in the terminal tool’s output. This makes debugging difficult as error messages that would normally appear in stderr are missing or not properly separated from stdout output.

The issue affects commands that write to stderr, including:

• Commands that fail and output errors
• Commands that intentionally write to stderr (e.g., using >&2 redirection)
• Scripts that output warnings or errors to stderr
• Commands with mixed stdout/stderr output

Expected behavior would be to capture both stdout and stderr streams separately, or at minimum display stderr output alongside stdout output.

Steps to Reproduce

1. Open Cursor IDE in Agent mode
2. Use the terminal tool to run a command that produces stderr output
   Example: Run a command that fails, or use: echo “error” >&2
3. Observe the terminal tool output
4. Notice that stderr output is either missing, not displayed, or not properly distinguished from stdout output

Expected Behavior

The terminal tool should properly capture and display both stdout and stderr output streams. Error messages written to stderr should be visible in the terminal output, similar to how a standard terminal would handle them. Ideally, stderr should be distinguishable from stdout (e.g., through different formatting or clear indication), but at minimum, all output should be captured and displayed.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.44 (user setup)
VSCode Version: 1.105.1
Commit: f6a8593b2b7c61c2063c79d5a8fcd248c9db4580
Date: 2025-12-01T22:52:09.315Z
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

Yes - Cursor is unusable

[Riaan_De_Winnaar]

[deanrie]

Hey, thanks for the report. From the description and Windows version (2.1.44), I see the issue with stderr handling in Agent Terminal - the new implementation sometimes loses or mixes stderr with stdout.

Temporary workaround:

• Settings Ctrl+Shift+J > Agents > Inline Editing & Terminal > enable “Legacy Terminal Tool”
• Cmd+Shift+P → “Terminal: Kill All Terminals”
• Restart Cursor

Could you please share:

• The exact command where stderr disappears (e.g., echo error 1>&2), and a comparison of output in Agent Terminal vs regular Terminal panel
• Your terminal profile (PowerShell/CMD/Git Bash/WSL)
• Screenshot of errors from Help > Toggle Developer Tools > Console during execution
• Agent launch Request ID (chat menu > Copy Request ID, Privacy Mode off)

Share the info, and I’ll pass it to the team.

[Riaan_De_Winnaar]

Thanks for the suggestion. No go through. Issue persists. I had one lucky chat window with auto… screenshot above, where the terminal responded. Stranded and cannot continue my work.

This is going to be messy, please excuse.

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! Install PowerShell on Windows - PowerShell | Microsoft Learn

PS> $PROFILE
C:\Users\riaan\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
PS> $PROFILE | Format-List -Force

AllUsersAllHosts : C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1
AllUsersCurrentHost : C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell_profile.ps1
CurrentUserAllHosts : C:\Users\riaan\Documents\WindowsPowerShell\profile.ps1
CurrentUserCurrentHost : C:\Users\riaan\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
Length : 75

PS> Test-Path $PROFILE
True
PS> New-Item -Path $PROFILE -ItemType File -Force

Directory: C:\Users\riaan\Documents\WindowsPowerShell

Mode LastWriteTime Length Name

---

-a---- 12/2/2025 11:07 AM 0 Microsoft.PowerShell_profile.ps1

PS>

Agent terminal codex 5.1, trying to find an issue, realises its terminal’s ■■■■■■.
$ python -c “import json, pprint; from pathlib import Path; data=json.load(open(‘ODDS_DATA/supersportbet_match_20251202_100057.json’,‘r’,encoding=‘utf-8’)); events=[e for e in data.get(‘events’,) if ‘Asteras Tripolis’ in e.get(‘event_name’,‘’) and ‘Ilioupoli’ in e.get(‘event_name’,‘’)]; print(‘events found’, len(events)); event=events[0] if events else None; markets=[m for m in (event.get(‘markets’,) if event else ) if m.get(‘market_type’)==‘home_total’]; print(‘home_total markets’, len(markets)); [print(‘line’, m.get(‘line_value’), ‘outcomes’, [(o.get(‘outcome_name’), o.get(‘odds’)) for o in m.get(‘outcomes’,)]) for m in markets];”*

$ python -c “print(‘hello’)”

$ python -c “import json, pathlib; from pathlib import Path; data=json.load(open(‘ODDS_DATA/supersportbet_match_20251202_100057.json’,‘r’,encoding=‘utf-8’)); events=[e for e in data.get(‘events’,[ ]) if ‘Asteras’ in e.get(‘event_name’,‘’) and ‘Ilioupoli’ in e.get(‘event_name’,‘’)]; event=events[0] if events else {}; out_lines=[ ]; out_lines.append(f’Events found: {len(events)}'); out_lines.append(f"Event name: {event.get(‘event_name’)}”); for market in event.get(‘markets’,[ ]):

$ python -c “import json; from pathlib import Path; data=json.load(open(‘ODDS_DATA/supersportbet_match_20251202_100057.json’,‘r’,encoding=‘utf-8’)); events=[e for e in data.get(‘events’,[ ]) if ‘Asteras Tripolis’ in e.get(‘event_name’,‘’) and ‘Ilioupoli’ in e.get(‘event_name’,‘’)]; lines=[f’Events found: {len(events)}‘]; event=events[0] if events else None; lines.append(f"Event name: {event.get(‘event_name’) if event else ‘None’}“); lines.append(f"Start: {event.get(‘start_time’) if event else ‘N/A’}”); [lines.append(f"Market: {m.get(‘market_type’)} line={m.get(‘line_value’)} outcomes={[(o.get(‘outcome_name’), o.get(‘odds’)) for o in m.get(‘outcomes’,[ ])]}") for m in (event.get(‘markets’,[ ]) if event else [ ]) if m.get(‘market_type’) in (‘home_total’,‘away_total’)]; Path(‘temp/asteras_supersportbet_dump.txt’).write_text(’\n’.join(lines), encoding=‘utf-8’)”

*$ python -c “from pathlib import Path; Path(‘temp/test_output.txt’).write_text(‘hello’,‘utf-8’)”

copied to user terminal
PowerShell Extension v2025.4.0
Copyright (c) Microsoft Corporation.*

PowerShell in Visual Studio Code

Type ‘help’ to get help.*

PS> python -c “from pathlib import Path; Path(‘temp/test_output.txt’).write_text(‘hello’,‘utf-8’)”
PS> python -c “import json; from pathlib import Path; data=json.load(open(‘ODDS_DATA/supersportbet_match_20251202_100057.json’,‘r’,encoding=‘utf-8’)); events=[e for e in data.get(‘events’,[ ]) if ‘Asteras Tripolis’ in e.get(‘event_name’,‘’) and ‘Ilioupoli’ in e.get(‘event_name’,‘’)]; lines=[f’Events found: {len(events)}‘]; event=events[0] if events else None; lines.append(f"Event name: {event.get(‘event_name’) if event else ‘None’}“); lines.append(f"Start: {event.get(‘start_time’) if event else ‘N/A’}”); [lines.append(f"Market: {m.get(‘market_type’)} line={m.get(‘line_value’)} outcomes={[(o.get(‘outcome_name’), o.get(‘odds’)) for o in m.get(‘outcomes’,[ ])]}") for m in (event.get(‘markets’,[ ]) if event else [ ]) if m.get(‘market_type’) in (‘home_total’,‘away_total’)]; Path(‘temp/asteras_supersportbet_dump.txt’).write_text(’\n’.join(lines), encoding=‘utf-8’)”
ParserError:
Line |
1 | … {m.get(‘market_type’)} line={m.get(‘line_value’)} outcomes={[(o.get(’ …
| ~
| Missing type name after ‘[’.
PS> python -c “import json, pathlib; from pathlib import Path; data=json.load(open(‘ODDS_DATA/supersportbet_match_20251202_100057.json’,‘r’,encoding=‘utf-8’)); events=[e for e in data.get(‘events’,[ ]) if ‘Asteras’ in e.get(‘event_name’,‘’) and ‘Ilioupoli’ in e.get(‘event_name’,‘’)]; event=events[0] if events else {}; out_lines=[ ]; out_lines.append(f’Events found: {len(events)}'); out_lines.append(f"Event name: {event.get(‘event_name’)}”); for market in event.get(‘markets’,[ ]):

out_lines.append(f"market: {market.get(‘market_type’)} line: {market.get(‘line_value’)} outcomes: {[(o.get(‘outcome_name’), o.get(‘odds’)) for o in market.get(‘outcomes’,[ ])]}“); Path(‘temp/asteras_supersportbet_home_total.txt’).write_text(‘\n’.join(out_lines), encoding=‘utf-8’)”
ParserError:
Line |
2 | … ‘market_type’)} line: {market.get(‘line_value’)} outcomes: {[(o.get(’ …
| ~
| Missing type name after ‘[’.
PS> python -c “print(‘hello’)”
hello
PS> python -c "import json, pprint; from pathlib import Path; data=json.load(open(‘ODDS_DATA/supersportbet_match_20251202_100057.json’,‘r’,encoding=‘utf-8’)); events=[e for e in data.get(‘events’,[ ]) if ‘Asteras Tripolis’ in e.get(‘event_name’,‘’) and ‘Ilioupoli’ in e.get(‘event_name’,‘’)]; print(‘events found’, len(events)); event=events[0] if events else None; markets=[m for m in (event.get(‘markets’,[ ]) if event else [ ]) if m.get(‘market_type’)==‘home_total’]; print(‘home_total markets’, len(markets)); [print(‘line’, m.get(‘line_value’), ‘outcomes’, [(o.get(‘outcome_name’), o.get(‘odds’)) for o in m.get(‘outcomes’,[ ])]) for m in markets];"python -c “import json, pprint; from pathlib import Path; data=json.load(open(‘ODDS_DATA/supersportbet_match_20251202_100057.json’,‘r’,encoding=‘utf-8’)); events=[e for e in data.get(‘events’,[ ]) if ‘Asteras Tripolis’ in e.get(‘event_name’,‘’) and ‘Ilioupoli’ in e.get(‘event_name’,‘’)]; print(‘events found’, len(events)); event=events[0] if events else None; markets=[m for m in (event.get(‘markets’,[ ]) if event else [ ]) if m.get(‘market_type’)==‘hom^C
PS> python -c "import json, pprint; from pathlib import Path; data=json.load(open(‘ODDS_DATA/supersportbet_match_20251202_100057.json’,‘r’,encoding=‘utf-8’)); events=[e for e in data.get(‘events’,[ ]) if ‘Asteras Tripolis’ in e.get(‘event_name’,’‘) and ‘Ilioupoli’ in e.get(‘event_name’,’')]; print(‘events found’, len(events)); event=events[0] if events else None; markets=[m for m in (event.get(‘markets’,[ ]) if event else [ ]) if m.get(‘market_type’)==‘home_total’]; print(‘home_total markets’, len(markets)); [print(‘line’, m.get(‘line_value’), ‘outcomes’, [(o.get(‘outcome_name’), o.get(‘odds’)) for o in m.get(‘outcomes’,[ ])]) for m in markets];”
events found 0
home_total markets 0
PS>

[Riaan_De_Winnaar]

Terminal state cleared! The orphaned terminal state files have been deleted.

What We Fixed

Found in logs: “Process had no disconnect runners but was an orphan”

• This means terminals were getting disconnected but their state persisted
• Cursor couldn’t properly spawn new shell processes for agent terminals

What we did:

1. Killed all Cursor processes
2. Deleted state.vscdb files that contained orphaned terminal state
3. Now restart Cursor

Test After Restart

When Cursor opens:

1. Open an agent window
2. Try a simple command: echo “test” or Get-Date
3. Check if you see actual output (not just the command echoed back)

If this still doesn’t work, then we have two options:

• Option A: Switch from pre-release → stable build (Settings → Updates → Release Track)
• Option B: Clean reinstall (but try Option A first)

Let me know if the terminal output works after restarting!

Let me restart windows. can you report all we have tried during this session?

● Complete Troubleshooting Session Report

Issue Identified

• Problem: Cursor agent terminal shows exit code 0 but captures no output (stdout/stderr)
• Scope: All Cursor agent models affected (auto works occasionally, Opus 4.5 never works)
• Root Cause: Orphaned terminal processes + incorrect terminal configuration

---

Fixes Applied

1. Deleted Corrupted workspaceStorage (First attempt)

Backed up to: workspaceStorage.backup.20251202_135209

Deleted: C:\Users\riaan\AppData\Roaming\Cursor\User\workspaceStorage

Result: Didn’t fix the issue

---

2. Investigated PowerShell Profile Issues

Found problems:

• direnv hook in C:\Users\riaan\Documents\PowerShell\Microsoft.PowerShell_profile.ps1
  • Line 13: Invoke-Expression “$(direnv hook pwsh)”
• Empty automation profile in Cursor settings
• Profile encoding issues in gh-copilot.ps1

User action: Disabled direnv extension in Cursor
Result: Didn’t fix the issue

---

3. Fixed Terminal Automation Profile

File: C:\Users\riaan\AppData\Roaming\Cursor\User\settings.json

Changed:
// FROM (empty):
“terminal.integrated.automationProfile.windows”: {

},

// TO (with -NoProfile flag):
“terminal.integrated.automationProfile.windows”: {
“path”: “C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe”,
“args”: [“-NoProfile”, “-NoLogo”]
},
Reason: Prevents PowerShell profile from interfering with agent terminal
Result: Applied but didn’t fully fix the issue

---

4. Disabled Terminal Preview Box

File: C: \Users\riaan\AppData\ Roaming\Cursor\User\settings.json

Changed:
// FROM:
“cursor.terminal.usePreviewBox”: true,

// TO:
“cursor. terminal.use PreviewBox”: false,
Reason: Known workaround for Cursor agent terminal output capture bug
Result: Applied (primary fix from Cursor forums)

---

5. Found Orphaned Terminal Processes

Evidence from logs:
C:\Users\riaan\AppData\Roaming\Cursor\logs\20251202T163626\ptyhost.log
[warning] Persistent process “1”: Process had no disconnect runners but was an orphan

Problem:

• Only 2 PowerShell processes spawned for 3 terminals
• Agent terminal had pid: -1 (no actual shell process)
• Terminal state database contained orphaned connections

---

6. Cleared Orphaned Terminal State

Killed all Cursor processes

powershell -Command “Get-Process Cursor -ErrorAction SilentlyContinue | Stop-Process -Force”

Deleted corrupted terminal state databases

rm -f “C:/Users/riaan/AppData/Roaming/Cursor/User/workspaceStorage//state.vscdb”
Files deleted:

• workspaceStorage/2055a6af195532040710a2ef2f58fb97/state.vscdb*
• workspaceStorage/dc0f699d70fcaf5984b152bfb0954b0f/state.vscdb*

Reason: Orphaned terminal state prevents new shell processes from spawning

---

Diagnostic Evidence

From Process Explorer:

• ptyHost.exe (18444) - Terminal manager
• conpty-agent.exe (3912, 28060) - Only 2 agents for 2 real terminals
• PowerShell.exe (7556, 21180) - Only 2 shells
• Missing: 3rd PowerShell process for agent terminal (Terminal 7)

From DevTools Console:

• OTLPExporterError: Bad Request - Telemetry errors (not root cause but indicates instability)

---

Primary Fixes (Most Likely to Work)

1. Cleared orphaned terminal state (state.vscdb files)
2. Disabled cursor.terminal.usePreviewBox (known workaround)
3. Added -NoProfile to automation profile (prevents profile interference)

---

Backup Files Created

All backups are in C:\Users\riaan\AppData\Roaming\Cursor\User:

• workspaceStorage.backup.20251202_135209/ (full workspace backup)
• settings.json.bak.* (multiple timestamped backups)
• settings.json.before_preview_fix (before usePreviewBox change)

---

If Issue Persists After Windows Restart

Option A - Switch to Stable Build:
Settings → Update: Release Track → “stable” (currently on “prerelease”)

Option B - Clean Reinstall:

1. Export settings: File → Preferences → Profiles → Export
2. Uninstall Cursor
3. Delete: C:\Users\riaan\AppData\Roaming\Cursor\
4. Reinstall from fresh download
5. Test with default settings first before restoring

---

Research Sources Referenced

• solved-terminal-output-not-showing-in-agent-mode-delete-workspacestorage-folder-v2-1-39-windows-11/
  144751
• How I Fixed the Cursor IDE Agent Terminal Output Bug: A Step-by-Step Troubleshooting Guide – Dre Dyson

---

Next Steps After Windows Restart

1. Open Cursor
2. Open agent window
3. Test with: echo “test” or Get-Date
4. Expected: See actual output, not just command echo
5. Report back results!

Good luck!

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
? for shortcuts

[markus-lassfolk]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor Agent Terminal Tool Bug Report

Summary

The Cursor Agent Terminal Tool (run_terminal_cmd) consistently fails to execute commands, returning exit code -1 with no output, regardless of command complexity or configuration.

Environment

• OS: Linux (WSL2 on Windows)
• Shell: Bash

Problem Description

All terminal commands executed via the agent terminal tool fail with:

• Exit Code: -1
• Output: Empty (no stdout, no stderr)
• Behavior: Commands appear to be sent but never execute or return results

This affects:

• Simple commands: echo "test", pwd, ls
• Environment-dependent commands: gh auth status
• Script execution: python3 script.py
• All command types regardless of complexity

Important Notes

Integrated Terminal Works

The integrated terminal (Terminal → New Terminal) works perfectly:

• Commands execute correctly
• Environment variables are available
• Tools like gh CLI work as expected
• This confirms the issue is specific to the agent terminal tool, not the environment

Configuration Attempts

We have tried multiple configuration approaches without success:

1. Terminal Settings (.vscode/settings.json):

   {
     "terminal.integrated.shellArgs.linux": ["--login"],
     "terminal.integrated.defaultProfile.linux": "bash",
     "terminal.integrated.inheritEnv": true,
     "terminal.integrated.automationProfile.linux": {
       "path": "/bin/bash",
       "args": ["--login"]
     },
     "terminal.integrated.env.linux": {
       "CURSOR_CLI": null,
       "CURSOR_AGENT": null
     },
     "terminal.integrated.shellIntegration.enabled": false
   }
   

2. Shell Configuration (~/.bashrc):

   • Added environment loading for non-interactive shells
   • Added Cursor agent detection to simplify shell behavior
   • Ensured .bash_env is sourced before interactive checks

3. Legacy Terminal Tool:

   • Enabled “Legacy Terminal Tool” in Cursor settings
   • Restarted Cursor multiple times
   • No change in behavior

4. Environment Setup:

   • Created ~/.bash_env for consistent environment across shell types
   • Updated ~/.profile to source environment
   • Verified environment works in integrated terminal

What Works

• Integrated terminal (user-visible terminal)
• Manual command execution in system terminal
• Environment configuration (PATH, variables, tools)
• GitHub CLI authentication (gh auth status works manually)

What Doesn’t Work

• Agent terminal tool (all commands fail)
• Command execution via AI agent
• Output capture from agent terminal

System Information

uname -a
Linux Markus-PC 6.6.87.2-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Thu Jun  5 18:30:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux 

echo $SHELL
/bin/bash

which bash
/usr/bin/bash

bash --version
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)

Additional Context

Shell Environment

• Default Shell: Bash
• Shell Config Files:
  • ~/.bashrc - Configured to load environment for non-interactive shells
  • ~/.bash_env - Contains PATH and environment variable setup
  • ~/.profile - Sources .bash_env for login shells

Workspace Details

• Path: /home/markusla
• Type: Home Assistant custom integration project
• Language: Python 3.x

Impact

This issue significantly impacts productivity:

• Cannot execute commands via AI agent
• Cannot run scripts or tools through agent
• Cannot verify command outputs
• Forces manual execution of all commands

Requested Resolution

1. Immediate: Fix agent terminal tool to execute commands and capture output
2. Investigation: Determine root cause of exit code -1 with no output
3. Documentation: Clarify if there are known limitations or requirements for agent terminal
4. Alternative: Provide workaround or alternative method for command execution

Reproduction Rate

• Frequency: 100% (all commands fail)
• Consistency: Reproducible across all command types
• Duration: Persistent across multiple Cursor restarts

Related Issues

This may be related to:

• Non-interactive shell execution in agent mode
• Environment variable handling in agent terminal
• Output capture/streaming issues
• Shell integration conflicts

Contact Information

• Workspace: /home/markusla/
• Ready to provide: Additional logs, system information, or test results as needed

Steps to Reproduce

1. Open Cursor IDE
2. Use the AI agent chat
3. Ask the agent to run any terminal command
4. Observe: Command returns exit code -1 with no output

Example commands that fail:

echo "test"
pwd
gh auth status
cd /path && python3 script.py

Expected Behavior

Commands should:

• Execute successfully
• Return appropriate exit codes (0 for success, non-zero for errors)
• Display stdout and stderr output
• Work consistently across all command types

Actual Behavior

• All commands return exit code -1
• No output is captured or displayed
• Commands appear to be sent but never execute
• No error messages are provided

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.0-pre.22.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: 1459faeb76c672cfa094b4b4d028112ec5f8bed0
Date: 2025-12-02T08:24:16.317Z
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.26220

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[user1340 (Dgkenn)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor’s integrated terminal does not capture or display output from executed commands, even though commands execute successfully (exit code 0). Commands complete with exit code 0 but NO OUTPUT is displayed. Affects Python, PowerShell, and CMD commands. External terminals work correctly.

Steps to Reproduce

1. Open Cursor’s integrated terminal (PowerShell)
2. Run: python -c “print(‘Hello World’)”
3. Run: Write-Host “Test”
4. Observe: Commands complete (exit code 0) but NO OUTPUT displayed
5. Same commands work correctly in external terminal

Expected Behavior

Terminal should display stdout/stderr output like external terminals do. When running python -c “print(‘Hello’)”, I should see “Hello” in the terminal.

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.26200

For AI issues: which model did you use?

All AI models

Does this stop you from using Cursor

Yes - Cursor is unusable

[Alex19 (Alex)]

same problem:

Cursor version 2.1.39 has terminal bug

Where does the bug appear (feature/product)? Cursor IDE Describe the Bug commands are executed inside terminal but actually not executed npm run builld → no response from terminal at all, so Claude 4.5 Sonnet confusing all time, like “why??” git status → no response git diff vite.config.ts → no response etc, every command Steps to Reproduce Just ask your agent to do some terminal stuff Expected Behavior responds command execution as same as previous Cursor version Screenshots / Screen Re…

[Riaan_De_Winnaar]

Real ■■■■ show, only way is to run the commands mannually and copy to the agent as mass block of tokens. Same issue, no output for the agent. exitcode 0. The terminal is broken in the latest 2 updates. Best to request a credit refund until the cursor resolves the issue.
tried every fix online. deleted workspace history, edited settings.json… None effective

[SmartManoj (மனோஜ்குமார் பழனிச்சாமி)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Empty outputs in agent terminal

Steps to Reproduce

prompt: run pwd

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.46 (system 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.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

[Riaan_De_Winnaar]

Same issue, not output for the agent. exitcode 0. The terminal is broken in the latest 2 updates. Best to request a credit refund, until the cursor resolves the issue.

[leetic3 (lee tice)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent doesn’t wait for terminal commands to run, instantly exits and tries moving on.

Happens in CMD and powershell.. auto and grok fast code 1… Did something recently change??

Steps to Reproduce

Asking it to run a command that takes a few seconds and doesn’t immediately output anything. In auto mode..

It is to wait and careful read terminal output.

Noticed issues last night.

Expected Behavior

Wait for command to run and not get stuck in Terminate batch job? Y/n

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.26200

For AI issues: which model did you use?

Auto, grok fast code 1

Does this stop you from using Cursor

No - Cursor works, but with this issue

[leetic3 (lee tice)]

It says terminal exited with code 0. It’s completely unusable right now.. not sure how others don’t have agent running and verifying commands outputs? Probably the single most powerful thing it does recursively with debugging..

[someone01]

@deanrie
I still dont understand this guy explain the bug and the root cause of it but it still not fixed
after his comment 2 updates were released but the issue is still there
and yes i tried legacy but nah didnt work

so can u fix it ASAP its annoying to manually follow the agent step by step just to unstuck it!

Version: 2.1.47 (system setup)
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
Date: 2025-12-04T02:31:50.567Z
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.26200

[deanrie]

Hey, thanks for pinging. The team is already working on the fix.

[John_Koenig]

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

[Nerfekk]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hello !
For the past 4 days, I’ve been experiencing an issue with PowerShell outputs in Cursor.
It can’t see the outputs, which means I can’t commit to Git and that’s a major problem.
I’ve installed all available updates Cursor, the PowerShell extension, and PowerShell itself on my machine but nothing has changed. The Cursor agent clearly tells me it’s encountering an issue with the API and cannot read the outputs, so no PowerShell command actually executes.

When I ask it to commit and push, I can see the commands being executed in the conversation, but the agent reports an output of 0, and no commit appears on Git.

Thanks !

Steps to Reproduce

When asking the Cursor agent to read a PowerShell output (for example, the latest Git commit hash), it won’t be able to do it.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.42 (system setup)
VSCode Version: 1.105.1
Commit: 2e353c5f5b30150ff7b874dee5a87660693d9de0
Date: 2025-12-01T02:18:26.377Z
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.26200

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

[Riaan_De_Winnaar]

Same story here, tried multiple fixes. Nothing worked. Windows.

For some reason, every now and then, auto gets output. The rest of the time, only exit codes. Its disbiltatating.

[deanrie]

Hey, thanks for the report. This is a known issue with the new terminal implementation on Windows - the agent can’t see PowerShell command outputs.

Temporary workaround:

1. Open Cursor settings Ctrl+Shift+J
2. Go to the Agents > Inline Editing & Terminal tab
3. Enable “Legacy Terminal Tool”
4. Press Ctrl+Shift+P > “Terminal: Kill All Terminals”
5. Fully restart Cursor

If that doesn’t help - try updating to version 2.1.46 (you have 2.1.42), this issue should be fixed there.

Similar: Agent unable to run commands on Windows 11 - fixed with Legacy Terminal Tool

And here: Cursor version 2.1.39 has terminal bug - fixed by updating to 2.1.46

If the problem persists, could you please share:

• Request ID of the problematic calls (in the chat menu > Copy Request ID)
• Screenshot of the chat window with the agent, showing “output: 0”

Let me know if this helped. If not, I’ll pass it to the team.

[Nerfekk]

Thank you for your prompt reply.

Unfortunately, even after updating Cursor and following your instructions, the bug still seems to be present.
Here is the Cursor version:
Version: 2.1.46 (system 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.26200

Here is the request ID:
2372d26e-7ebb-46e4-acf3-b09aa51ff73f

Attached is a screenshot of the agent confirming that no output is visible (output 0) :

I look forward to hearing from you.
Thank you!