For me, this issue actually got resolved in 1.6.46, however, updating to the latest 1.7.x actually regresses and the issue occurs again. Very frustrating I have to downgrade to preserve terminal visibility when it was actively fixed in a previous version, and now is no longer visible in the latest release.
Same. Working on 1.6.x, broken in 1.7.x.
Havenât downgraded because there are too many great upgrades in 1.7.x; so I prefer to have the annoyance of copying/pasting while this gets fixed.
Upgrading to 1.7.44 seems to have partially fixed the issue. I can now attach terminals to a chat by clicking the â@â symbol, go through terminals and selecting them. However, typing @terminal and selecting one does NOT add it to the chat.
Neither for me 
Version: 1.7.44
VSCode Version: 1.99.3
Commit: 9d178a4â â â 89981b62546448bb32920a8219a5d0
Date: 2025-10-10T15:43:37.500Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin x64 24.6.0
1.7.46 now. No change compared to Agent loses terminal output - #28 by laszlovandenhoek . Still need to manually add the terminal to the chat, typing â@â and selecting it doesnât work.
Another issue: âkillingâ a sandbox terminal by clicking the trash can icon doesnât actually terminate the process that it is running. I have to manually pkill it.
Same issues for me in:
Version: 1.7.46
VSCode Version: 1.99.3
Commit: b9e5948c1ad20443a5cecba6b84a3c9b99d62580
Date: 2025-10-14T01:21:46.830Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin x64 24.6.0
Still happening in:
Version: 1.7.52
VSCode Version: 1.99.3
Commit: 9675251a06b1314d50ff34b0cbe5109b78f848c0
Date: 2025-10-17T01:41:03.967Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin x64 24.6.0
@deanrie any updates on this? Still unable to move beyond version 1.6.x as I rely a lot on agents being able to iterate in the terminal in my workflow
1 Like
I am having this issue too, on all recent versions (2.0 now). The agent executes a command, i see the output while its running but when the command is finished the output dissapears, the agent doesnât receive it.
This is extremely annoying because now i cantât use any terminal commands.
I run mac Macbook pro M2 chip, on Tahoe 26.0.1 with the most recent Cursor version.
Please cursor team resolve this issue
Also echoing that this problem still exists on 2.0, regardless of having legacy terminal switched on or off.
I got it fixed by removing .vscode dir on every project dir (linux arch, version 1.7.54). I had previously tried deleting the profile dir to no avail.
That didnât work for me, even after reloading Cursor.
@deanrie gentle poke on this one since weâre several people interested in this fix, and it seems like a recurring issue that keeps happening to more and more users.
I am still having this issue.. Cursor team please fix it
FIY i always use grok code maybe that matters ?
I ended up removing my /users/me/Application Support/Cursor folder on mac and fresh boot cursor and so far so good!
Iâm having the same issue in Cursor 2.1.49. The terminal run commands, but the agent does not see the output (no matter how I set the options in settings). When I copied the project to a new folder, the output briefly worked again, then stopped once more.
Anyone know whatâs causing this or how to fix it?
Update:
After some testing, it looks like Cursor wasnât just failing to capture terminal output â it was failing to run commands at all.
To verify this, I removed bun from my system and asked the agent to run the project build. Cursor reported that everything was fine, even though bun was definitely never executed. I repeated this multiple times: no errors, no output, and the command was clearly not being run.
Then I enabled Debug mode in the settings, and suddenly the issue disappeared. Now, when I trigger a build, Cursor correctly reports that bun is missing and tries to fix it. I even turned Debug mode off and restarted Cursor, and it still works.
So I still donât know what exactly causes the problem or whether Debug mode truly fixes it, but it seems the root issue is not terminal output â itâs that the agent fails to execute programs until something (like enabling Debug mode) resets its state.
This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.