Cursor cuts off the last output line of Agent Terminal

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Steps to Reproduce

Ask the agent to run git status in legacy terminal in an empty repository - he will say that he received an empty output, although you will see a one-line output of the command

Expected Behavior

I don’t need to fight with my IDE.

Screenshots / Screen Recordings

2025-12-08_10-49-07.png
2025-12-08_10-49-07.png1126×869 27.4 KB

Operating System

Windows 10/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.22631

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey @Artemonim!

I’ll repeat what my colleague @condor asked for in your other thread:

Could you post a Request ID with privacy disabled so we can look into the details? Cursor – Getting a Request ID

Once you provide that, we can investigate further!

3

RID: f2c0305c-215b-4c9a-8d08-ccb042a0826c

[10 tools called]

Echo/Write-Output checks ran in PowerShell from G:\GitHub\LivingLayers. Observations:

  • Echo-only sequences printed their lines (minor truncation on the final item when many were chained).
  • Write-Output-only sequences showed the first two items; the third line appeared truncated/absent.
  • Mixed with Write-Output last: only the echo line appeared; the trailing Write-Output line was not visible.
  • Mixed with echo last: only the Write-Output line appeared; the final echo line did not show.
  • Suggest using echo (or Write-Host) for reliable visibility in this terminal.

Changes Made: None.
Unfulfilled Tasks: None.
Manual Changes Required: None.
Special Attention Required: Output capture for Write-Output appears unreliable when mixed; verify with echo/Write-Host if exact visibility matters.

Version: 2.2.1 (user setup)
VSCode Version: 1.105.1
Commit: da7d015bb36ac403cb47ce878bffd5d7bc735e40
Date: 2025-12-09T16:08:10.218Z
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.22631
4

Hey @Artemonim

Sorry for the delay here. Indeed, looking into the logs I can see the missing final line of your scripts.

I’m still having trouble reproducing this on my end. Could you explain why you’re using the Legacy Terminal Tool? Do you have different behavior locally when you switch it off?

5
  1. The new terminal launches in read-only mode, which prevents the user from entering any commands into the same terminal.
  2. Based on the previous point, if the Agent accidentally or intentionally runs a command that requires user input, the command cannot be executed. Also, I cannot send a KeyboardInterrupt signal.
  3. The new terminal does not monitor running processes, leaving behind zombie processes.
  4. The new terminal ignores color coding, which reduces the convenience and speed of reading the terminal output for the user.

I filed bug reports about all these problems as soon as the new terminal was released in Early Access, and the only solution offered by the team was a button to switch back to the legacy terminal.

The only thing I don’t like about the legacy terminal is the inability to disable the auto-kill process function, which can kill the terminal during long compilations or manual testing.

1 Like